Connect agent harnesses

Your Familiar can hand a task to an agent running on your own computer and bring the result back into the conversation. OpenCircle calls these local agents agent harnesses.

Open Connections → Agent harnesses in OpenCircle Desktop and set up whichever agent you actually use — you don't need all of them. Keep that Desktop connected to your Server while it works. Adding a model-provider key in Server admin does not by itself complete this setup; these connections use accounts and software on your own desktop.

Connect a CLI coding agent

Turn on the agent's switch, then follow its runtime section: use a detected compatible install, or let OpenCircle install a reviewed runtime for you. Sign in through the account flow the card opens in your browser — the first connected account becomes the default, and adding a later account is your choice. Confirm the card shows the agent ready and available for new work.

Choose permissions deliberately

Most agent cards offer a default mode, an ask-for-changes mode, and a full-access mode. Full access lets the agent run commands and edit files without OpenCircle approval or sandboxing — OpenCircle asks you to confirm that choice explicitly. Changing the default account or permissions only affects new work, not a task already running.

Give your Familiar a first task

In a private conversation, name the agent, the project, and the result you want, for example:

Use the connected coding agent to inspect the project in ~/Projects/sample-app. Explain how to run it and suggest one small improvement. Don't change any files yet.

A ready connection is just the setup check; a completed task is what proves it can do useful work. For repository or remote-machine work, also set up GitHub CLI or SSH access.

When an agent is unavailable