Skip to content
Seggo

Claude Code

Status: history is read, and Claude Code can be turned on.

Where its history lives

Section titled “Where its history lives”
macOS Windows
~/.claude/projects %USERPROFILE%\.claude\projects

If you set CLAUDE_PROJECTS_DIR or CLAUDE_CONFIG_DIR, Seggo uses that instead.

What Seggo reads

Section titled “What Seggo reads”
  • Each project’s session files, including subagent sessions.
  • Files are opened read-only. Seggo never writes to ~/.claude while reading.

What turning it on changes

Section titled “What turning it on changes”

Only after you confirm the preview:

What Where
Seggo’s MCP entry ~/.claude.json (moves with CLAUDE_CONFIG_DIR if set)
Rules section CLAUDE.md in each chosen project
Session-end hook .claude/settings.local.json in each chosen project

The session-end hook saves a basic handoff automatically when a session ends. Reading context, claiming tasks and the fuller handoff rely on the rules section.

Try it

Section titled “Try it”

In a project you turned on, run claude, do something small, then ask:

Save a Seggo handoff for this work.

The handoff appears under Threads for that project in Seggo.

Notes

Section titled “Notes”
  • If your CLAUDE.md is a link to AGENTS.md, Seggo won’t write through the link. Turn on Codex for that project to add the section to the real AGENTS.md.
  • If you set CLAUDE_CONFIG_DIR, Seggo expects .claude.json to move with it. We haven’t confirmed this yet. If it doesn’t work, tell us at contact@bozomalabs.com.