TheDocumentation Index
Fetch the complete documentation index at: https://docs.remoteagent.chat/llms.txt
Use this file to discover all available pages before exploring further.
claude-sdk runner uses Anthropic’s @anthropic-ai/claude-code Node.js SDK directly within the agent process — no subprocess, no CLI binary, no shell invocation. The model runs in-process, which means lower latency, better error handling, and access to the full SDK feature set including tool use and streaming.
Requirements
- An Anthropic API key (
sk-ant-...). Get one at console.anthropic.com. - No additional binary to install. The SDK runs in-process within the RemoteAgent.CHAT binary.
Setup
Duringremoteagent init, choose claude-sdk from the interactive list. When prompted for your API key, paste your Anthropic key:
~/.remoteagent/agents/{agentId}.json on your local machine. It is never transmitted to RemoteAgent.CHAT servers. Each project can use a different key — useful if you have multiple projects billed to separate Anthropic accounts.
To use this runner from the command line without the interactive wizard:
How it works
When your agent receives a command, theclaude-sdk runner calls the @anthropic-ai/claude-code SDK with the prompt and the current working directory. The SDK handles:
- Model selection (latest Claude model configured in the SDK)
- Tool use (file read/write, bash execution, etc.)
- Streaming output chunks back to the agent
Pros and cons
| Pros | Cons |
|---|---|
| Best output quality — full SDK capability | Requires a paid Anthropic API key |
| Lowest latency — no subprocess overhead | API usage is billed per token |
| Best error handling and retry logic | — |
| Access to all Claude tools (bash, file I/O) | — |
| No extra installation step | — |
API key security
The key is stored in plain text in the config file. Make sure~/.remoteagent/ has appropriate permissions: