Claude Code

Claude Code

Claude Code is Anthropic's CLI coding agent. It runs as a process in its own Daintree terminal panel with full PTY emulation, like every other built-in agent.

Install & Authenticate

Anthropic's native installer is the recommended path. The npm package installs the same binary and is what Daintree offers from the in-app install prompt.

curl -fsSL https://claude.ai/install.sh | bash

irm https://claude.ai/install.ps1 | iex

curl -fsSL https://claude.ai/install.sh | bash

Run claude once and follow the browser prompts. Claude Code needs a Pro, Max, Team, Enterprise, or Console account; setting ANTHROPIC_API_KEY works too. Daintree reads that state from ~/.claude.json, ~/.claude/config.json, or ANTHROPIC_API_KEY to decide whether the agent shows as ready.

Daintree also probes the native installer's own locations — ~/.local/bin/claude on macOS and Linux, %LOCALAPPDATA%\claude-code\bin\claude.exe on Windows — so a native install is still detected when the Electron process inherits a PATH that misses it.

How Daintree Launches It

Claude Code declares no inline-rendering flag, so it takes the alternate screen buffer the way its own CLI does, whatever the global "use alt-screen mode by default" switch says. Turning on permission bypass adds --dangerously-skip-permissions to the launch.

Six provider templates ship with the agent: Anthropic (native), Z.AI, OpenRouter, DeepSeek, Ollama, and a custom OpenAI-compatible endpoint. Create a preset From template and the non-secret environment variables (base URL, model aliases, timeout) are pre-filled, with API key fields left blank for you. See Presets.

Daintree's unified input completes Claude's / commands from its built-in catalog plus the custom commands and skills it finds under .claude/commands and .claude/skills, honoring CLAUDE_CONFIG_DIR. /goal is offered for Claude Code and Codex alike.

Resuming Sessions

Daintree mints the session ID itself and hands it to Claude Code at launch with --session-id <uuid>, rather than scraping it back out when the session ends. That is why a Claude session survives a crash, a force quit, or a SIGKILL: the ID was recorded before the CLI ever produced output.

Later relaunches reuse that same ID with claude --resume <session-id>. An ID can only be assigned to a new conversation, so Daintree assigns once and resumes thereafter. If the ID is lost anyway, the fallback is --continue, which reopens Claude's most recent session in that directory. For the resume mechanics across all agents, see Session Resume.