Runtimes
A worker is an identity Korps keeps: a name, a manager, a team, objectives and history. A runtime is the agent that runs it. A model is what it thinks with. Change either and the worker is still the same worker.
Hermes Agent comes bundled and is the recommended start. OpenClaw, Agent Zero, Nanobot and ZeroClaw are in launch scope, each marked with what Korps can say about it today. Coding agents bring their own access: Claude Code a Claude subscription or Anthropic Console account, Cursor a Cursor account, OpenAI Codex a ChatGPT plan or OpenAI API key, and OpenCode a model provider account of your own. Whichever you choose, install it on the machine you pair, sign in once, and Korps drives it like any other worker; the model it thinks with is an AI provider account you connect, on your own key or sign-in. Provider credentials for agents on your connected machine stay on that machine. Credentials added through Korps Cloud compute connections are encrypted and stored by Korps.
Accounts, subscriptions and keys are pools. When one runs out, the work moves: the worker keeps its name, its manager, its objective and its history. Only the compute changes. Scripted demo
A worker acts on a machine. Today that machine is one you pair with the app. Hosted execution, where Korps runs the machine for you, is the next step for Korps Cloud and is not available yet.
Ask for a pairing code in the app, run the pairing command on the machine, and it appears in your workspace. From then on its health is what it last reported, and every worker on it says which machine it is on.
Model keys never travel: a connection records which provider a worker uses and where the key lives, and Korps refuses a request that carries one.
Create the free account now. When the app opens, pair a machine, sign in to the agent you already use, and hire the first worker.
