Catervas Join the waitlist

Security

How agents are kept apart.

Catervas makes one promise: an agent cannot use what belongs to another agent. This page says how far that promise goes, and where it stops.

What is separate

Every agent has its own:

The keys and sign-ins you give Catervas are kept in an encrypted vault on your computer, and each agent is handed only its own.

Two ways to run an agent

As an ordinary program on your computer

This is the simplest way, and the usual one. The agent gets its own folders and its own sign-ins, and Catervas points the agent program at them.

It is not a sandbox. The agent runs under your user account, as any program you start does. Catervas keeps agents from being given each other's sign-ins. It does not stop a program that sets out to read other files your account can read. Run agents this way when you trust the agent program and the work you give it.

In its own Docker container

A container is a sealed box on your computer with its own files and its own network. An agent in a container sees only what was put in the box. Choose this when you want a real wall around an agent, for example when it works on code you have not read.

Agents ask before they act

You choose for each agent how much it may do without asking. An agent set to ask shows you each file it wants to change and each command it wants to run, and waits for your answer.

Sharing is something you choose

Agents in the same workspace share one GitHub account, one set of connections and skills, and the workspace's documents and whiteboards. That is the purpose of a workspace. Agents in different workspaces, and agents in none, share nothing.

What has been proven, and what has not

Catervas is in pre-release. Separation between agents is checked by tests that start two agents with different everything and confirm, from inside each one, that the other's connections, skills, sign-ins and files cannot be seen. It has also been tried with real agents on Linux.

Some parts have not yet been run against the real service: signing in to GitHub, the Discord connection, and running on macOS. We will say so here until they have been.

Reaching your agents from Discord or Slack

This is optional. If you turn it on, what you and your agents say there is stored by Discord or Slack, as every message on those services is. Anyone who gets into the Discord or Slack account you linked can direct your agents, so protect that account with two-step sign-in.

Catervas Cloud

The cloud service is planned and not built. The plan is that each agent runs in a container of its own, that an agent's sign-ins are handed to it only while it is awake, and that they are never stored with its files. This page will describe what is built once it exists.

Reporting a security problem

If you find a way for one agent to reach what belongs to another, or any other security problem, please write to security@catervas.example before telling anyone else, so that it can be fixed first. We will answer, and we will credit you if you would like that.