Claude Code
Install, authenticate, verify, and run Claude Code through Synara.
Synara connects to the Claude Code runtime installed on your machine. Claude owns the account, model access, tools, and authentication; Synara owns the task, working environment, transcript, approvals, review surfaces, and Git lifecycle around the session.
Install
Use Anthropic’s current setup instructions. A common package-manager installation is:
npm install -g @anthropic-ai/claude-codeSynara looks for the claude executable. It can also use a native or Homebrew installation when that executable is available to the desktop process.
Verify the installation:
claude --versionDo not use sudo npm install -g. Fix the package-manager permissions or use an official alternative instead.
Authenticate
Start Claude Code in a terminal:
claudeComplete the authentication path appropriate to your setup. Claude Code supports Claude account subscriptions, Anthropic Console access, and supported enterprise backends such as Amazon Bedrock or Google Vertex AI.
Where supported by your installed version, inspect authentication directly:
claude auth statusSynara does not copy or replace Claude credentials.
Verify
Before opening Synara, verify Claude Code from a fresh terminal in a test repository:
cd /path/to/test-repository
claude --version
claudeAsk a harmless read-only question, then exit. This checks the binary, authentication, repository access, and provider service independently of Synara.
Connect to Synara
Open provider settings
Enable Claude Code and confirm that Synara detects the runtime.
Check the executable
Automatic discovery should resolve claude. Configure a custom binary path only when you intentionally use another installation.
Refresh models
Confirm that the model picker shows the models and effort options exposed by your account and installed runtime.
Start a bounded task
Use a small objective in a clean repository before enabling broader permissions or parallel work.
Capabilities in Synara
Claude Code sessions can expose provider-specific behavior through Synara, including:
- Model and effort selection
- Plan and execution modes
- Tool calls, file changes, and command output
- Approval requests and user questions
- Resumable sessions
- Claude subagents and tracked tasks where supported
- Context-usage information where available
- Native steering of a running turn
Native steering means a follow-up can be delivered to supported live Claude sessions without first cancelling the active turn. The provider still decides when and how to act on it.
Claude capabilities change with the installed CLI and account. Treat the controls shown in your current Synara session as authoritative for that runtime.
Updating
Synara can recognize common npm, Homebrew, and native Claude installations. Depending on the installation source, update Claude Code through its package manager or:
claude updateRestart Synara after replacing the executable.
Troubleshooting
Claude is not detected
- Run
claude --versionfrom a fresh terminal. - Compare the resolved executable with the custom binary path in Synara.
- Restart Synara after changing
PATHor installing Claude. - Remove an obsolete custom path rather than pointing Synara at a wrapper that no longer exists.
Claude is detected but not authenticated
Run claude directly and complete the provider’s own login flow. For enterprise backends, verify the required cloud credentials and environment variables in the same shell environment.
Models or effort options are missing
Update Claude Code, confirm the account exposes the expected model, and refresh provider status. Model availability is account- and runtime-dependent.
A session behaves differently from the Claude terminal
Compare the selected model, permission mode, project settings, local instructions, and executable path. A different Claude installation or configuration source can produce different behavior.
Official documentation
Continue with Your first task or Provider handoffs.