Launching November 3, 2026
Corv Client

Corv Client

The SSH client for AI agents and humans.

FreeAI AgentsAIOpen Source472 impressionslaunches Nov 3

The SSH client for AI agents and humans. Connect by name. Reuse authenticated SSH connections. Keep secrets local. AI agents don't use SSH the way humans do. Plain SSH exposes credentials to the caller, returns terminal text that agents must parse, re-authenticates every command, and relies on tmux, nohup, or custom scripts for long-running tasks. Corv is built for agent-driven infrastructure. It lets agents connect by name, execute commands without exposing passwords or private keys, receive structured JSON output, reuse a warm authenticated connection, and detach and resume long-running jobs. Humans use the exact same connections through an interactive terminal UI.

Corv Client is an SSH client that lets AI agents and humans run commands over warm, encrypted connections with structured JSON output.

for
Developers building AI agents or scripts that need secure, reusable SSH access.
pricing
open source
license
Apache-2.0
khalid-src/corv-client 9 0Goupdated a month ago
works withOpenSSH multiplexingssh-agent

Key features

8 features of Corv Client
  • Named connection profiles — Save and reuse SSH connections by name for both agents and humans.
  • At-most-once execution — Idempotency keys ensure mutating commands are safe to retry.
  • Encrypted secret store — Passwords and keys are stored encrypted and never exposed on the command line.
  • Structured JSON output — Command stdout/stderr are de-noised, bounded and returned as JSON.
  • Detached long-running jobs — Jobs survive client or network loss and can be re-attached via run ID.
  • Cross-platform binary — Single dependency-free executable works on Linux, macOS and Windows.
  • Local crash-safe state — Connection, vault and job state are written atomically to survive crashes.
  • Integrated diagnostics — Commands like corv test and corv doctor provide structured connection health checks.

Use cases

  • Run periodic maintenance scripts on production servers from an AI orchestrator
  • Deploy applications via CI pipelines without exposing SSH keys
  • Monitor and retrieve logs from remote hosts with bounded JSON output
  • Resume long-running data migrations after a network interruption

Corv Client vs alternatives

Corv ClientLangChainDopplerClaude CodeDocker
Best forAgent-driven SSH executionLLM app frameworkSecrets managementAI coding assistantContainerization
PricingOpen sourceFreeSubscriptionSubscriptionSubscription
DevHunt upvotes10000
LaunchedNov 2026————

Corv Client FAQ

How does Corv keep credentials secret?+

Credentials are stored in an encrypted local vault (DPAPI, Keychain, or 0600 file) and never appear on the command line or in logs.

Can I use Corv with existing ~/.ssh/config?+

Yes, you can import hosts from ~/.ssh/config using corv import and then manage them through the UI or CLI.

What happens if a command crashes or the client disconnects?+

Jobs are detached and recoverable; you can re-attach with the run ID or retrieve bounded output later.

Is Corv safe for mutating operations?+

Provide an idempotency key via --run-key to guarantee at-most-once execution even on retries.

Do I need a daemon or background service?+

No, Corv runs as a single binary without any daemon; a local broker is started on demand.

How is output size limited?+

Corv bounds output to a head and tail (up to 20 MiB stored locally) and de-noises ANSI sequences.

Summarized by DevHunt from github.com · Oct 7, 2026. Details may change; check the official site.