Claude Code is Anthropic’s CLI coding agent.
Setup
The first time you launch a Claude Code session, CliDeck shows a setup toast. Click Patch Claude and CliDeck adds lifecycle hooks to ~/.claude/settings.json. Claude will ask for one-time approval on next launch.
These hooks give CliDeck deterministic start/stop/idle signals — no polling, no heuristics.
What Works
- Status detection — Hook-driven. CliDeck receives direct signals when Claude starts working, stops, goes idle, or shows a choice menu
- Message preview — The sidebar shows the latest output line (identified by the
⏺ marker)
- Session resume — Session IDs are captured from telemetry for seamless resume
- Notifications — Get notified when Claude Code finishes a task
Session Resume
When you close CliDeck (or it shuts down), your Claude Code sessions are saved automatically. Next time you open CliDeck, you’ll see them in the Previous Sessions section of the sidebar. Click the resume button to pick up where you left off.
Behind the scenes, CliDeck captures the session ID from Claude Code’s telemetry and uses claude --resume <sessionId> to reconnect.
Telemetry Details
CliDeck sets these environment variables when launching Claude Code:
| Variable | Value |
|---|
CLAUDE_CODE_ENABLE_TELEMETRY | 1 |
OTEL_LOGS_EXPORTER | otlp |
OTEL_EXPORTER_OTLP_PROTOCOL | http/json |
OTEL_EXPORTER_OTLP_ENDPOINT | http://localhost:4000 |
OTEL_LOGS_EXPORT_INTERVAL | 2000 |
These tell Claude Code to send OpenTelemetry logs to CliDeck’s local receiver every 2 seconds. The data never leaves your machine.
If Claude Code releases a major update that changes its telemetry format, you may need to update CliDeck. Check for the latest version with npm update -g clideck.