Agents

TurnPanel does not contain an agent. It runs the ones you already use, in your spaces, and gives them the same memory, skills, tools and browser.

Pick your agents during setup and TurnPanel installs them into your first space. Later, a space admin can add, update or remove agents in the space's settings under Harnesses. Versions are pinned, so nothing updates on its own.

You sign in to each agent once, through that agent's own login, from any space where it is installed or from your profile. Your jobs then use your account in every space you open. Someone else's sign-in is never visible to you, and yours is never visible to them. An admin can remove a person's sign-in but cannot see or use it.

How it works depends on the agent: a link and a code to enter, a link and a box to paste a code into, or an API key that you save as your own secret. The dialog walks you through it. TurnPanel keeps the sign-in encrypted and hands it only to your own processes of that agent.

pi uses TurnPanel's model picker (see Models). Every other agent uses its own models, listed after you sign in, with options such as effort. TurnPanel does not route their requests.

A Claude Code in your own terminal or an editor can connect to a space too. Paste the space's MCP address and a key into any MCP client. Everything such an agent does is limited by the key. A command that sets this up for you, turnpanel connect, is not available yet.

Every agent knows it can start another job on any agent and model the space allows. A space admin can limit which ones, in the space's settings under Models.