neo sessions
Upload your Claude Code, Codex and Antigravity sessions to the forge.
setup installs agent hooks that upload each session, redacted on this machine, to the repositories it touched; list, visibility and delete manage what is there. What is sent and who can see it: neo docs agent-sessions.
neo sessions [OPTIONS] <COMMAND>neo sessions setup
Section titled “neo sessions setup”Install the Claude Code, Codex and Antigravity hooks and turn uploads on for this host.
Adds a neo sessions hook entry to Claude Code’s settings.json (Stop and SessionEnd), Codex’s hooks.json (Stop, plus features.hooks = true in config.toml), and Antigravity’s hooks.json (Stop), keeping every other setting and hook (any previous file is saved beside it as <name>.neo.bak), and records your consent for this host. Running it again changes nothing.
neo sessions setup [OPTIONS]neo sessions disable
Section titled “neo sessions disable”Remove the agent hooks and turn uploads off for this host.
Removes only the entries setup added. Sessions already uploaded stay; delete them with neo sessions delete.
neo sessions disable [OPTIONS]neo sessions status
Section titled “neo sessions status”Show whether uploads are on, the latest uploads and skips, and whether your commit email links commits to your account
neo sessions status [OPTIONS]neo sessions upload
Section titled “neo sessions upload”Upload sessions now.
The hook runs this on its own. By hand it uploads the named sessions, or every session changed within --since, whether or not setup was run. A session that touched no repository on this forge, or that you deleted, is skipped.
neo sessions upload [OPTIONS] [SESSION_ID]...| Option | Value | Required | Default | Env | Values | Description |
|---|---|---|---|---|---|---|
<SESSION_ID> |
no | Agent session ids (from Claude Code, Codex or Antigravity) | ||||
--since |
<DURATION> |
no | Also upload every session changed within this window: a number and a unit, s, m, h, d or w (e.g. 7d) |
|||
--force |
no | Re-send even when the bundle is unchanged since the last upload, so the forge re-checks the session’s links (use after a forge upgrade). Consent, the host check, deleted sessions and sessions that touched no repository on this forge are still skipped |
neo sessions list
Section titled “neo sessions list”List your uploaded sessions, newest first
neo sessions list [OPTIONS]| Option | Value | Required | Default | Env | Values | Description |
|---|---|---|---|---|---|---|
--json |
no | Print the server’s JSON objects instead of the table |
neo sessions visibility
Section titled “neo sessions visibility”Change who can see one of your sessions.
Only signed-in users who can read (or write) EVERY repository the session touched see it; you always do.
neo sessions visibility [OPTIONS] <ID> <VISIBILITY>| Option | Value | Required | Default | Env | Values | Description |
|---|---|---|---|---|---|---|
<ID> |
yes | The session: its forge id or its external session id | ||||
<VISIBILITY> |
yes | private, writers, readers |
Who can see it besides you |
neo sessions delete
Section titled “neo sessions delete”Delete one of your sessions from the forge.
The forge refuses it from then on, and this machine stops offering it.
neo sessions delete [OPTIONS] <ID>| Option | Value | Required | Default | Env | Values | Description |
|---|---|---|---|---|---|---|
<ID> |
yes | The session: its forge id or its external session id |