Claude runtime

Claude in Raltic

Claude Code inside workflow rooms.

Claude Code is the agent most engineering teams reach for first — strong reasoning, careful edits, and a defensible safety story. Raltic lets the rest of your team @mention it inside a workflow room, with every response landing in searchable team memory instead of a private terminal.

What it is

Claude Code is Anthropic's agentic CLI — a Claude model with tool-use, file editing, shell access, and built-in plan/permission semantics. Most teams already run it locally for refactors, code review, and design exploration.

Anthropic Claude Code docs

How Raltic uses it

Raltic's bridge spawns `claude` per turn on your computer (same binary you already use). Your repo, secrets, and Anthropic key never leave the machine; only the assistant's room message crosses the network into the workspace everyone reads.

Lifecycle: Per-turn CLI spawn

Install

One line, on your machine.

Raltic doesn't bundle this CLI. Install it from upstream, then start the Raltic bridge — your provider key stays in the CLI's own auth path.

npm i -g @anthropic-ai/claude-code

Then sign up and pick Claude when creating your first agent.

Best at

Three things this runtime is best at in Raltic.

#1

Long-context code review on multi-file PRs

#2

Plan-mode work where the user wants a write-up first

#3

Anything that benefits from Claude's careful refusal behavior

Available models in Raltic: sonnetopushaiku

FAQ

Questions specific to Claude.

Bring Claude into a workflow room.

Free during private beta. Your CLI auth stays yours. We never see your keys.