How do I install the Session Info skill?

Run npx skillmds@latest add tomevault-io/session-info in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Session Info safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Session Info?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Session Info free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Session Info?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Session Info by tomevault-io — Agent Skill

Name: Session Info
Author: tomevault-io

Session Info

This skill should be used when the user asks "what's my session ID?", "show my inbox topic", "get session info", "what session am I in?", "my agent ID", or needs to retrieve current hive session details for messaging coordination or debugging. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Session Info - Get Current Session Details

Display information about the current hive session, including session ID, inbox topic, and state.

Terminology

Session - An isolated git clone + terminal environment managed by hive
Session ID - A unique 6-character identifier (e.g., 26kj0c)
Agent - The AI tool (Claude, Aider, etc.) running within the session
Inbox - A message topic for receiving messages: agent.<session-id>.inbox

When to Use

Need to know current session ID
Another agent asks for inbox topic
Setting up inter-agent coordination
Debugging messaging issues
Verifying correct session context

Commands

Get Session Info (Human-Readable)

hive session info

Example output:

Session ID:  26kj0c
Name:        claude-plugin
Repository:  hive
Inbox:       agent.26kj0c.inbox
Path:        /Users/hayden/.local/share/hive/repos/hive-claude-plugin-26kj0c
State:       active

Get Session Info (JSON)

hive session info --json

Example output:

{
  "id": "26kj0c",
  "name": "claude-plugin",
  "repository": "hive",
  "inbox": "agent.26kj0c.inbox",
  "path": "/Users/hayden/.local/share/hive/repos/hive-claude-plugin-26kj0c",
  "state": "active"
}

Output Fields

Field	Description	Example
`id`	Unique 6-char session identifier	`26kj0c`
`name`	Human-readable session name	`claude-plugin`
`repository`	Git repository name	`hive`
`inbox`	Full inbox topic	`agent.26kj0c.inbox`
`path`	Absolute path to session directory	`/Users/...`
`state`	Session state	`active`, `recycled`, `corrupted`

Session States

active - Normal, working session ready for use
recycled - Session has been stopped and cleared
corrupted - Session directory or files are damaged

Common Workflows

Share Inbox with Another Agent

hive session info --json | jq -r '.inbox'
# Output: agent.26kj0c.inbox

Extract Session ID for Scripting

SESSION_ID=$(hive session info --json | jq -r '.id')
INBOX=$(hive session info --json | jq -r '.inbox')

Verify Session Before Messaging

# Check session context is correct
hive session info

# Then check inbox
hive msg inbox

How Session Detection Works

The command detects the current session from the working directory. Sessions are identified by:

Working directory path within a hive session directory
Session directory pattern: $XDG_DATA_HOME/hive/repos/<repo>-<session-id>
.hive-session file in the directory

If not in a hive session directory, the command fails with an error.

Additional Resources

For troubleshooting and advanced usage, see:

references/troubleshooting.md - Common issues and solutions

Related Skills

/hive:inbox - Check inbox for messages
/hive:publish - Send messages to other agents' inboxes
/hive:wait - Wait for messages on inbox

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: session-infodescription: This skill should be used when the user asks "what's my session ID?", "show my inbox topic", "get session info", "what session am I in?", "my agent ID", or needs to retrieve current hive session details for messaging coordination or debugging. Use when this capability is needed.---# Session Info - Get Current Session DetailsDisplay information about the current hive session, including session ID, inbox topic, and state.## Terminology- **Session** - An isolated git clone + terminal environment managed by hive- **Session ID** - A unique 6-character identifier (e.g., `26kj0c`)- **Agent** - The AI tool (Claude, Aider, etc.) running within the session- **Inbox** - A message topic for receiving messages: `agent.<session-id>.inbox`## When to Use- Need to know current session ID- Another agent asks for inbox topic- Setting up inter-agent coordination- Debugging messaging issues- Verifying correct session context## Commands### Get Session Info (Human-Readable)```bashhive session info```**Example output:**```Session ID: 26kj0cName: claude-pluginRepository: hiveInbox: agent.26kj0c.inboxPath: /Users/hayden/.local/share/hive/repos/hive-claude-plugin-26kj0cState: active```### Get Session Info (JSON)```bashhive session info --json```**Example output:**```json{ "id": "26kj0c", "name": "claude-plugin", "repository": "hive", "inbox": "agent.26kj0c.inbox", "path": "/Users/hayden/.local/share/hive/repos/hive-claude-plugin-26kj0c", "state": "active"}```## Output Fields| Field | Description | Example ||-------|-------------|---------|| `id` | Unique 6-char session identifier | `26kj0c` || `name` | Human-readable session name | `claude-plugin` || `repository` | Git repository name | `hive` || `inbox` | Full inbox topic | `agent.26kj0c.inbox` || `path` | Absolute path to session directory | `/Users/...` || `state` | Session state | `active`, `recycled`, `corrupted` |## Session States- **active** - Normal, working session ready for use- **recycled** - Session has been stopped and cleared- **corrupted** - Session directory or files are damaged## Common Workflows### Share Inbox with Another Agent```bashhive session info --json | jq -r '.inbox'# Output: agent.26kj0c.inbox```### Extract Session ID for Scripting```bashSESSION_ID=$(hive session info --json | jq -r '.id')INBOX=$(hive session info --json | jq -r '.inbox')```### Verify Session Before Messaging```bash# Check session context is correcthive session info# Then check inboxhive msg inbox```## How Session Detection WorksThe command detects the current session from the working directory. Sessions are identified by:1. Working directory path within a hive session directory2. Session directory pattern: `$XDG_DATA_HOME/hive/repos/<repo>-<session-id>`3. `.hive-session` file in the directoryIf not in a hive session directory, the command fails with an error.## Additional ResourcesFor troubleshooting and advanced usage, see:- **`references/troubleshooting.md`** - Common issues and solutions## Related Skills- `/hive:inbox` - Check inbox for messages- `/hive:publish` - Send messages to other agents' inboxes- `/hive:wait` - Wait for messages on inbox---> Converted and distributed by [TomeVault](https://tomevault.io/claim/colonyops) — claim your Tome and manage your conversions.

Frequently asked questions