Providers

A provider tells the daemon which interactive process to start in a checkout. Shell is built in; Codex and Claude Code use separately installed native CLIs and the provider's existing authentication.

Shell provider

Shell launches the platform's normal interactive shell inside the selected checkout and requires no agent account.

sylvops session create \
  --worktree <WORKTREE_ID> \
  --provider shell \
  --name "Build and test"

Shell sessions support interactive input, terminal resize, detach, reconnect, bounded scrollback, and complete process-tree termination.

Codex provider

Codex requires a separately installed native Codex CLI and an existing sign-in. Follow the official Codex CLI installation guide, then authenticate outside SylvOps:

codex login
codex login status

The official OpenAI documentation explains ChatGPT and API-key authentication. Never paste credentials into SylvOps.

Claude Code provider

Claude Code requires an official native Claude Code CLI version 2.1.145 or newer. Follow the official Claude Code setup guide, then authenticate outside SylvOps with Claude.ai or Anthropic Console:

claude --version
claude auth login
claude auth status

SylvOps accepts the first-party authentication methods reported by Claude Code. Third-party gateways, Amazon Bedrock, Google Vertex AI, and other enterprise authentication modes are outside the current provider contract.

Discovery and retry

At daemon startup, SylvOps searches bounded, supported locations for native provider executables. Discovery considers an explicit absolute override, PATH, official native and package-manager layouts, and supported npm layouts. It verifies that the executable is a native binary for the current operating system and architecture.

Shell shims, desktop-app binaries, WSL paths from Windows, links that escape a supported install root, and executables with the wrong architecture are rejected. After discovery, SylvOps uses bounded probes equivalent to:

codex --version
codex login status

claude --version
claude auth status

The desktop and TUI Refresh provider health action and these commands refresh discovery rather than relying on a cached miss:

sylvops provider probe codex
sylvops provider probe claude

Starting an agent

The desktop and TUI session forms offer every healthy enabled provider plus an optional display name. The CLI also supports model, effort, and initial-prompt fields:

sylvops session create \
  --worktree <WORKTREE_ID> \
  --provider codex \
  --model <MODEL> \
  --effort high \
  --prompt "Review the current task and implement it"

sylvops session create \
  --worktree <WORKTREE_ID> \
  --provider claude \
  --model sonnet \
  --effort high \
  --prompt "Review the current task and implement it"

Claude effort accepts low, medium, high, xhigh, or max. The initial prompt is passed to the process but excluded from persisted provider arguments, prompt history, logs, audit events, and SQLite.

Attention and permissions

SylvOps adds an application-owned, daemon-lifetime settings layer when it launches Claude Code. It observes bounded lifecycle events so clients can surface permission requests, user questions, subagent activity, background work, completion, and recoverable failures.

These hooks are observational. They do not approve or deny permissions, answer questions, change Claude's permission mode, or edit the user's, project's, or organization's Claude settings. If Claude Code does not establish a verified session identity within 15 seconds, SylvOps shows recovery guidance while leaving the terminal attached and usable.

Resume

When Codex or Claude Code reports a verified external session ID and the source session is eligible, SylvOps can create one successor session:

sylvops session resume <SESSION_ID>

Resume is guarded by the original provider and checkout identity. Claude resumes the exact verified conversation with --resume; SylvOps does not select Claude's continue-latest, named-session, or fork-session behavior.

Troubleshoot Codex

Codex is missing

available: false with no executable path means SylvOps could not find a supported native executable.

1. Run codex --version in a normal terminal.
2. Install or repair Codex using the official guide.
3. Restart the daemon or refresh provider health.
4. Run sylvops provider probe codex again.

Codex login is required

When Codex is available but authenticated: false, the executable was found but codex login status did not report a usable sign-in.

1. Run codex login outside SylvOps.
2. Confirm codex login status succeeds.
3. Retry the SylvOps provider probe.

Troubleshoot Claude Code

Claude Code is missing or too old

Run these commands outside SylvOps:

claude --version
sylvops provider probe claude

Install or update the official native CLI if it is missing or older than 2.1.145, then refresh provider health.

Login is required or unsupported

claude auth login
claude auth status
sylvops provider probe claude

Sign in with Claude.ai or Anthropic Console. A third-party or enterprise authentication method can make Claude Code usable on its own while remaining unsupported by SylvOps.

SylvOps does not install or update provider CLIs, initiate login, repair credentials, or select provider permission modes.

Not included

Claude cloud sessions, background-agent management, Remote Control, plugins, and enterprise authentication are not part of the current Claude Code provider. GitHub, Cursor, Pi, and remote providers are also not current public features.