Remote Coding Terminal for AI Agents · ● attached · 4 hosts · 6 sessions
You Are The Ultimate Agent.
The models are good at typing. You are the one who knows what should be
built. The Architect gives you one console for every harness you already run —
attached over SSH, inside the screen and tmux sessions you
already keep alive.
No orchestration layer. No opinion about your workflow. Just direct hands on every agent you have running, from whichever device is in front of you.
One line per job: project, last output, elapsed time. When a session rings the terminal bell, the badge lights and decays over sixty seconds — so you can tell an agent that wants you now from one that wanted you an hour ago, without opening anything.
Your ideas don't have session limits.
Claude Code taps out its session limit mid-task. Aider hits a rate limit. Every harness runs out eventually — but the project you handed it doesn't reset just because the tool did.
The Architect tracks the project, not the agent. Point a different harness at the same host, the same directory, the same environment, and pick up exactly where the last one stopped.
- claude-code
- Runs until its session limit, same as any tool.
- aider
- Picks up the same project the moment Claude Code taps out.
- openai-codex / opencode / pi
- Same host, same directory, no reconfiguration.
- your own command
- Anything that runs in a terminal counts as a harness.
A session limit is the tool's problem, not yours.
The Architect doesn't pick a favorite harness. It tracks the project — the host, the directory, the environment — and lets you point whichever agent is free at it, the instant the last one stops.
Rate limits happen. Losing the thread of what you were building shouldn't.
Rate limits stop tools. Not you.
From empty list to connected in under a minute.
Three things, set up once. Point a harness at a host, give a project somewhere to live, then pair the two to start a job — that pairing is what actually launches the session.
01 — Add an agent
Add the SSH credentials for a host running your harnesses. These are the workers you command.
02 — Create a project
Name the idea, then give it a directory or use a git clone URL to make the directory. This is where the work lives and gets done.
03 — Start a job
Start the agent session on your project. Now your session is named and the agent is ready to work on that project anytime you are.
Set up once. Reuse forever.
Native on whatever device you are using.
Not a stripped-down companion app on the phone and a real one on the desktop. The same terminal engine everywhere — the navigation adapts, the capability does not.
Not a browser tab pointed at a terminal.
Set the environment before you connect.
Every serious harness is configured through its environment. Which endpoint it talks to, which model it asks for, which key it authenticates with, which proxy it goes through — all of it arrives as variables, and all of it has to be right before the process starts, because none of it can be changed once the tool is running.
So you set it on the agent, not in a .bashrc you have to remember
to edit on four different machines. The Architect exports your variables into the session,
then runs your start script, then launches the tool — in that order, every time.
One place, per agent, under your control.
# exported before the tool starts ANTHROPIC_BASE_URL=https://llm-gw.internal:8443 ANTHROPIC_API_KEY=sk-ant-•••••••••••• ANTHROPIC_MODEL=claude-opus-5 OPENAI_BASE_URL=http://workstation.lan:11434/v1 HTTP_PROXY=http://proxy.lan:3128 NO_PROXY=localhost,127.0.0.1,.internal TERM=xterm-256color COLORTERM=truecolor
Point a harness anywhere
A base URL is just a variable. Send one agent through your company gateway, another at a model running on the box down the hall, a third at a staging endpoint you are evaluating — same tool, three agents, no reconfiguration between them.
Keys per agent, not per machine
Each agent carries its own set. A host shared across projects does not need one
global key in a shell profile, and rotating a key is one edit in one place instead of
an ssh round trip to every machine.
A start script for the rest
Whatever variables cannot express — activate a virtualenv, change into the project directory, warm a cache. It runs after the exports and before the tool, so the harness comes up in the state you meant. An end script runs when you disconnect.
One place. Full control.
Your config syncs through your own server.
There is no sync service, because there is no server of ours to sync to.
The Architect writes your agent and project configuration — environment blocks
included — as JSON over SFTP into ~/.thearchitect/ on a host you
already own, and reads it back on the next device. That is the whole mechanism.
Push
Export agents and projects to any host you can reach. Hosts, ports, session managers, tools, env vars, start and end scripts.
Pull
Point a new install at the same host. The first-run wizard lists what is there and imports what you pick.
Never SSH credentials
Your SSH passwords and private keys are excluded from the transfer by design. They stay in the device keystore and are never written to a host — not even the host you are exporting to. Your environment variables do travel, into your own home directory on your own machine, because that is what makes a new device work on arrival.
Same idea for keys: the app generates an RSA-2048 and an ECDSA P-256
identity pair on first launch, copies the public line to your clipboard, or appends it to a
host's authorized_keys over a password session — so you can move to key
auth without leaving the app.
It does not care who you are.
The Architect has no idea what your name is, and has no way to find out. There is nothing to log into and nothing that phones home.
- □ No account, no sign-in, no profile The app ships without a login screen. There is no identity to create, verify, recover, or breach.
- □ SSH credentials never leave the keystore Private keys and passwords go to the platform keystore — Keychain, Credential Manager, libsecret — and are read only to open your own connection. Never the app database, never a config file, never written to a host, never sent anywhere.
- □ Traffic goes to your hosts and nowhere else Every connection is a direct SSH session from your device to your machine. No relay, no proxy, no broker in the middle.
- □ Licensing is offline Pro is unlocked by a platform-locked key validated on-device. No activation call, no seat server, no license check that can fail while you are on a plane.
- □ No telemetry Nothing measures how you use it. If you want a record of a session, turn on traffic logging and it writes to a file on your own disk.
Start for free.
One agent and one project, free forever, with every feature on this page working. It is enough to attach to a real host and decide for yourself.
Find it useful? Upgrade to Pro right from the app — pricing is listed in each store.