Reference

Claude subscription mode

Run new chats as the raw Claude Code terminal so usage stays on your subscription's interactive limits.

Claude subscription mode is an experimental setting that changes how Kalauz runs agents. Instead of Kalauz's own chat UI, each new chat opens the real Claude Code terminal — the same TUI you'd get running claude yourself — inside the workspace's worktree.

Why it exists

By default, Kalauz drives Claude non-interactively (claude -p, the Agent SDK path) and renders the stream in its own chat UI. That path is metered differently from interactive use:

Starting June 15, 2026, Agent SDK and claude -p usage on subscription plans draws from a new monthly Agent SDK credit, separate from your interactive usage limits.

So heavy automated runs can exhaust that separate credit while your normal interactive allowance sits untouched. Claude subscription mode sidesteps it: by running the interactive Claude Code TUI, your usage counts against the same limits as using claude in a terminal by hand — your Claude Pro or Max interactive allowance — rather than the Agent SDK credit.

Turning it on

Open Settings → Experimental and enable Claude subscription mode.

Experimental features are under active development — expect breaking changes.

What changes

With it on, every new chat is created as a raw Claude Code terminal running:

claude --dangerously-skip-permissions

in the workspace's worktree, with the Claude Code TUI in the tab in place of Kalauz's chat UI. You drive Claude exactly as you would in a terminal.

The setting is captured per session, at creation time, so toggling it never disturbs chats you already have open — existing chats keep whichever mode they were created in. Switch the toggle, then open a new chat to get the new behavior.

Trade-offs

Running the raw TUI means you trade some of Kalauz's chrome — the structured transcript, inline diff comments wired back to the agent, per-message stats — for billing that stays on your interactive subscription. The workspace itself is unchanged: still an isolated worktree on its own branch, still reviewable and shippable from the detail panel.

What's next?