An SSH client for working on production servers, by hand or through AI agents. Agents get a terminal. They never get a password.

Coming soon to Windows and macOS. iOS and Android after that.

Every command passes through Valakes on its way to a server. Safe ones go straight through, passwords are filled in on the way, and dangerous ones wait for you.

A terminal first, with a command line under it

You type into the composer under the terminal. Before a command leaves, Valakes reads it: fills in the password, checks it for danger and knows which server it is going to. When vim, htop or a password prompt takes over, your keys go straight to the terminal.

It reads the command, not the text

Every command is parsed with a real bash grammar before it runs. The rules match the parsed command, so rm behind sudo or a find that deletes is caught, and the same words inside a quoted string are left alone.

LowPrints a line. Nothing to stop.

HighA card with the number of files it would delete.

HighDeletes what it finds, so it is checked like rm.

HighRuns a download nobody has read.

MediumA note under the composer. It does not stop you.

Agents get a terminal, never a password

Claude Code, Codex, Cursor and anything with function calling connect through MCP or a REST API that listens on 127.0.0.1 only. Each agent has its own token and name. Its sessions open as tabs you can watch, and its commands go through the same checks as yours.

Agent policy for lab-staging

What happens to each agent call under the chosen policy
Agent callWhat Valakes does

A new host starts at Off, and a production host stays at Off until you change it. Read-only is a list of commands, not a sandbox: on production the real guard is a server user with fewer rights.

Ten tools, and none of them returns a secret

  • list_hostshosts, tags and the agent's policy
  • open_sessionopens a tab you can see
  • close_sessioncloses it
  • run_commandexit code, directory, time and output
  • read_outputthe rest of a long output, in parts
  • get_screenthe screen of vim, htop and the like
  • send_keysCtrl+C, arrows, text
  • list_credentialsnames only, never values
  • upload_filealways asks first
  • download_filealways asks first

Output is masked before an agent reads it

An agent writes {{cred:pg-staging}} and Valakes types the password itself. When a known password shows up in the output, the agent gets *** instead.

Printed on the server

$ cat /srv/app/.env
APP_ENV=staging
DATABASE_URL=postgres://app:Vx9-pq2r-77@db.internal/app
REDIS_PASSWORD=hT4-rr0-qq1

Read by the agent

$ cat /srv/app/.env
APP_ENV=staging
DATABASE_URL=postgres://app:Vx9-pq2r-77@db.internal/app
REDIS_PASSWORD=hT4-rr0-qq1

Masking covers the passwords in Valakes' vault. It cannot know other secrets a server prints, which is why policies and approvals exist.

Fast, because the terminal came first

Before any smart feature, v1 got speed budgets, and every stage had to stay inside them. Each bar is the full budget. The bright part is what the final v1 build used.

58.2 MB/s of sustained output while a 50 MB file scrolls by. The window keeps answering the whole time.

95th percentile, cold start is the median. Windows 11, Intel Core i7-14700KF, an SSH server in local Docker, final v1 build, 15 November 2026.

Where it stands

Started on 12 November 2026. Each stage ends with a manual acceptance test, and the next one starts only after it passes.

  1. 0

    Skeleton

    Electron, xterm.js with WebGL, an installer, a Docker SSH server for tests.

  2. 1

    SSH terminal

    Hosts, import from ~/.ssh/config, keys, ssh-agent, jump hosts, host key checks, tabs, Ctrl+K.

  3. 2

    Composer

    The command line, command blocks with exit codes, history, Tab completion that asks the server quietly.

  4. 3

    Credentials

    An encrypted vault, passwords bound to hosts, auto-fill, masking on screen and in history.

  5. 4

    Command check

    Risk rules, blast radius, production raising the level, confirmation of multi-line paste.

  6. 5

    Agent API

    MCP and REST, tokens, host policies, the approval queue, the audit log, masking.

  7. 6

    Design and release

    The Graphite interface, settings, signing, automatic updates, the Windows installer.

  8. 7

    File manager

    Two panes over SFTP, uploads and downloads, a typed host name before deleting on production.

  9. 8

    Built-in assistant

    A chat inside the app on your own API key, under the same rules as any outside agent.

Questions about Valakes

Short answers about what Valakes is, how AI agents use it and what keeps your servers and passwords safe.

What is Valakes?

Valakes is an SSH client for Windows and macOS made for working on production servers. A command line under the terminal fills in passwords, checks each command for danger before it runs and marks production hosts in red. AI agents can work on your servers through it without ever seeing a password.

How do AI agents like Claude Code and Codex connect to Valakes?

Through MCP or a REST API. Claude Code, Codex and Cursor start a small bridge program, valakes-mcp, which passes their calls to the running app. Anything with function calling can use the REST API instead. The API listens on 127.0.0.1 only, and every agent has its own token and name.

Can an AI agent see my server passwords?

No. An agent writes {{cred:name}} in a command, and Valakes types the password itself at the moment of use. None of the ten agent tools returns a secret, and every password Valakes knows is replaced with *** in the output before the agent reads it.

How does Valakes stop an AI agent from running rm -rf on production?

Every host has an agent policy: Off, Read-only, Approve writes or Full, and a new host starts at Off. High-risk commands such as rm -rf, DROP DATABASE or curl piped into sh never run without your approval, and for rm, chmod -R and chown -R Valakes counts on the server how many files the command would touch.

Does Valakes work with my existing SSH setup?

Yes. Valakes imports hosts from ~/.ssh/config and works with key files, ssh-agent and jump hosts. Host keys are always checked: an unknown host shows its fingerprint before the first connection, and a changed key stops the connection.

When will Valakes be released?

Valakes comes out for Windows and macOS first, soon. iOS and Android follow after that. Leave your email on this page to get one email on release day and one more when the phone apps are ready.

Coming soon

Valakes comes out for Windows and macOS first. iOS and Android follow. Leave your email, and we will write on release day, and once more when the phone apps are ready.

  1. First

    Windows and macOS

  2. After that

    iOS and Android

Release news only. We send a link to confirm first, and every email has a link to unsubscribe. What we keep