Commands and files
The two commands, where things are kept, and the limits in one place.
connecto
Available inside every terminal. See Agents using other terminals.
connecto list connecto send <id> [--ask] connecto result <request> connecto read <id> connecto keys <id> <key>... connecto watch <id> connecto unwatch <id> connecto add claude|codex|shell [--name <text>] connecto start <id> connecto close <id> connecto automation check [path] [--screen <file>] connecto package check [id|path]
connecto-app
From the downloaded app it is /Applications/Connecto.app/Contents/MacOS/connecto-app; the connecto command inside agent terminals is provided by the app, not installed on your PATH.
| Command | What it does |
|---|---|
connecto-app | Starts the app and restores your workspace. |
connecto-app --project <folder> | Starts the app and opens that folder as well. |
connecto-app provision | For scripts: copies your installed CLIs into Connecto's store (the app does this by itself at its first launch). Run it again to pick up a newer version of a tool. |
connecto-app audit verify <file> | Checks that an audit log has not been edited. |
Where things are kept
The data folder
~/Library/Application Support/connecto/
| Path | Holds |
|---|---|
workspace.json | Open projects, their order and names, and the ten most recent. |
settings.json | App settings: Connecto Home, launch modes, the utility model. |
cli/ | Connecto's copies of the agent CLIs. |
projects/<id>/settings.json | A project's tools, config modes and packages. |
projects/<id>/profiles/<tool>/ | The private profile of an isolated project. |
projects/<id>/history/ | Closed terminals and their transcripts. |
automations/history.jsonl | The record of automation calls. |
audit/ | Audit logs, one file per launch. |
remote/ | Remote access settings and the keys that may connect. |
Where secrets are kept
The Jev key, this machine's device keys, the relay token and the keys of paired machines are kept in one file, secrets/secrets.json in the data folder. Only your account can read it: on a Mac the file is readable by you alone (mode 600, in a folder of mode 700), and on Windows it sits in your own %APPDATA%. It is replaced in one step on every change, so it is never left half written. This is how command-line tools such as gh, ssh and aws keep their credentials, and it means Connecto never asks for Keychain access.
To keep secrets in the system store instead, turn on Settings → Remote Access → Store secrets in the system keychain (on Windows: Store secrets in Windows Credential Manager). The change takes effect at the next start, which moves the secrets across. Turning it off again moves them back to the file.
Up to 0.1.7 the secrets were in the Keychain. The first start of 0.1.8 reads that Keychain item once, writes the file and deletes the item, so macOS asks one last time. If you refuse, Connecto starts with no secrets and does not ask again: this machine gets a new device identity, so paired machines have to be paired again, and the relay token and the Jev key have to be entered again.
Connecto Home
The folder you chose in Settings.
| Path | Holds |
|---|---|
automations/<name>/automation.json | One automation. |
packages/<id>/ | One package. |
In each project
| Path | Holds |
|---|---|
.claude/, .codex/, .agents/ | Your own files, plus the ones packages installed. |
.connecto/packages.lock | Which files Connecto installed, so updates leave yours alone. |
Limits
| What | Limit |
|---|---|
| Terminals in a project | 16 open |
| Terminal name | 64 characters |
| A message between agents | 4096 bytes after redaction |
| Closed terminals kept per project | 500, transcripts up to 2 MiB each |
| Automatic key sequences into one terminal | 5 a minute, then automations stop for it |
| Classifier calls | 20 a minute, across all terminals |
| Screen text sent to the classifier | The bottom 60 lines, at most 6000 characters |
| A package | 2000 files, 16 MiB |
| A pairing code | Two minutes, one device |
| Remote users on a host | One at a time |