Claude Code
Confabulous has first-class support for Claude Code sessions.
What gets parsed
Section titled “What gets parsed”- Full conversation history (user, assistant, tool calls, tool results).
- Token counts per message (input, output, cache read, cache write).
- Model identifier per message.
- Tool invocations and their arguments.
- File edits and reads.
Analytics cards
Section titled “Analytics cards”Each Claude Code session produces these cards:
- Tokens — input/output/cache breakdown.
- Cost — using the pricing table.
- Tools — which tools were called and how often.
- Conversation — turn structure, active time, message counts.
- Repo activity — files touched, language breakdown.
Pricing
Section titled “Pricing”Confabulous tracks pricing for every published Claude model. New models are added to the pricing table as Anthropic publishes them.
Multiple backends
Section titled “Multiple backends”You can point separate Claude Code config dirs at separate Confabulous backends from one machine — for example, a personal CLAUDE_CONFIG_DIR that syncs to one backend and a work one that syncs to another. Bind a config dir to a backend at setup:
confab setup --provider claude-code --config-dir <dir> --backend-url <url>--config-dir requires --provider. Your default config dir keeps using the backend from your original confab setup, so existing single-dir setups are unaffected.
Other supported providers
Section titled “Other supported providers”Confabulous treats every provider as a first-class citizen. Codex, Cursor, and OpenCode are also supported today. New providers slot into the same sync, storage, and analytics pipeline.