AIToday
Large Language ModelsAI Coding AssistantsOpen-Source AIHacker NewsPublished: Jul 25, 2026, 04:00 JST

Corv v1.1 SSH client for AI agents now supports detached jobs and warm connections

Corv v1.1 SSH client for AI agents now supports detached jobs and warm connections

3 Key Points

  1. What happened

    Corv v1.1, an SSH client designed for AI agents, was released with features including connection reuse through a local broker, structured JSON output, detached long-running jobs with resume capability, and encrypted credential storage. Agents can execute commands by connection name without exposing passwords or private keys.

  2. Why it matters

    AI agents (Claude, Codex, and others) traditionally struggle with SSH—they must manage authentication, connection details, and terminal parsing themselves. Corv eliminates that overhead by providing a unified interface that keeps secrets local, reuses warm authenticated connections to avoid repeated setup costs, and returns structured output agents can parse directly. This reduces the infrastructure burden on agent workflows across Windows, macOS, and Linux.

  3. What to watch

    The tool is available for immediate install via curl, PowerShell, or Go (go install github.com/khalid-src/corv-client/cmd/corv@latest). Ready-to-use integrations for Claude and Codex are included in the repository (integrations/claude/corv-ssh and integrations/codex/AGENTS.md). The local broker automatically exits after 15 minutes of idle time and installs nothing on the remote server.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

Corv addresses a gap in how AI agents interact with infrastructure. SSH is designed around human workflows—users manage keys, negotiate interactive prompts, and parse terminal output—but agents need programmatic interfaces, credential isolation, and connection efficiency. Raw SSH invocations force agents to either handle authentication state themselves or expose secrets in command-line arguments, both poor for security and state management.

The local broker model solves connection reuse without requiring server-side changes (OpenSSH ControlMaster works on Unix but not Windows). By holding one authenticated connection per profile and multiplexing commands over that connection, Corv avoids repeated SSH handshakes and authentication. Detached job support is critical for long-running workflows: agents can start a deployment or install script, poll its status asynchronously, and resume output retrieval at any point, with bounded output handling (first 4 MiB + final section for large logs) so agents do not exhaust memory on verbose remote tasks.

The structured JSON output (with fields like exit_code, original_bytes, saved_bytes, returned_bytes, truncated, and output_truncated) gives agents the metadata they need to determine success, detect truncation, and decide whether to re-query or proceed. The integration paths for Claude and Codex suggest the tool is positioned for immediate adoption in agent-driven infrastructure workflows.

FAQ
How do I install Corv?
On Linux/macOS, run curl -fsSL https://raw.githubusercontent.com/khalid-src/corv-client/main/install.sh | sh. On Windows PowerShell, run irm https://raw.githubusercontent.com/khalid-src/corv-client/main/install.ps1 | iex. Alternatively, use Go: go install github.com/khalid-src/corv-client/cmd/corv@latest.
How do detached long-running jobs work?
If a command is still running after the broker's wait window, Corv returns bounded output, the run id, and exit code 75. Re-run the same command to attach to the existing job and see the next output delta. When the job finishes, Corv retains up to 20 MiB of output locally; if larger, it keeps the first 4 MiB and final section with an omission marker.
Where are credentials stored?
Passwords and key passphrases are stored in a local encrypted vault. On Windows, the vault key is protected by DPAPI. On macOS and Linux, Corv reads a provisioned Keychain/Secret Service key when present, otherwise uses a 0600 key file. Secrets are never passed on the command line or exposed in logs.
What platforms are supported for remote execution?
Remote command execution requires a POSIX shell and standard Unix command-line tools. Windows OpenSSH servers are not supported as remote execution targets. The local broker runs on Windows, macOS, and Linux consistently.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleResearcher builds compiler turning computation graphs into transformer weights—no training needed