Claude Desktop
Status: can be turned on. Seggo doesn’t read Claude Desktop’s history. Handoffs it saves arrive in Seggo directly.
How it works
Section titled “How it works”Claude Desktop has no history folder that Seggo reads. Instead, once it’s turned on, you ask Claude to save a handoff, and it goes straight into Seggo:
Save a handoff of this work to Seggo.
What did I last save in Seggo for the example-app project?
The handoff shows up in Seggo labelled with the tool that saved it.
How Seggo finds it
Section titled “How Seggo finds it”Seggo marks Claude Desktop as Found when the app or its settings folder exists. It only checks that they exist. Nothing inside them is read.
What turning it on changes
Section titled “What turning it on changes”Only after you confirm the preview:
| Settings file | |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows (Microsoft Store app) | %LOCALAPPDATA%\Packages\Claude_*\LocalCache\Roaming\Claude\claude_desktop_config.json |
| Windows (other installs) | %APPDATA%\Claude\claude_desktop_config.json |
Seggo adds only its own seggo entry and leaves the rest of the file as it
was. Restart Claude Desktop afterwards so it picks up the change.
- Claude Desktop has no project rules file, so there’s no rules section. Ask for a handoff when you want one.
- Seggo stays on your computer, but Claude Desktop still sends what Seggo returns to its model, as with any tool.
- Seggo’s Claude Desktop setup follows the settings file above. We haven’t confirmed this yet. If it doesn’t work, tell us at contact@bozomalabs.com.