Sign in and start the agents

By the end of this page the agents' commits show as verified, the box is signed in to Claude, its agent server is running under systemd, and nucleated is reporting on it. These are the steps that need you in person.

On this page

Register the signing key on GitHub #

Agents' commits are signed, so they show as Verified under your name. The playbook made the key on the box. You register its public half on GitHub as a signing key only: it can mark a commit as yours, but it cannot log in to GitHub or push.

The first command gives gh on your workstation the one permission it needs for this:

Workstation
gh auth refresh -h github.com -s admin:ssh_signing_key
Workstation
ssh agentbox-agent cat .ssh/id_ed25519_signing.pub > /tmp/agentbox-signing.pub
Workstation
gh ssh-key add /tmp/agentbox-signing.pub --type signing --title "agentbox agent signing"

Sign in to Claude #

Log in to the box as the agents' user and start Claude Code:

Workstation
ssh agentbox-agent
Boxas agent
claude

It prints a sign-in link. Open it on your workstation and sign in with the account for whoever this box works for. That login is the environment you named main in your settings.

Still in that session, run /mcp and authorise each connector that asks. Connectors follow the login, but some need authorising once per machine, and that cannot be done from a phone. Leave with /exit.

Start the agent server once by hand #

The first start asks two questions that a service cannot answer. Run the server yourself, once, in the nucleus:

Boxas agent
cd ~/workspace && claude remote-control --spawn worktree --no-create-session-in-dir --no-chrome
  1. Answer y to trust the folder.
  2. Answer y to enable Remote Control.
  3. Wait until it says it is connected.
  4. Stop it with Ctrl+C.

Hand over to systemd #

Each environment's agent server is a systemd user unit named agent-server@<environment>.service. The playbook enabled yours; start it:

Boxas agent
systemctl --user start agent-server@main.service
Boxas agent
systemctl --user status agent-server@main.service --no-pager

It should say active (running). From now on it starts at every boot, waits for the internet, and restarts itself if the server exits.

The server is a terminal program, so its unit runs it inside tmux. To see the server's own screen:

Boxas agent
tmux -L agent-main attach

Press Ctrl+B then D to leave it running.

Check nucleated #

The playbook installed and started the daemon. Check it is running:

Boxas agent
systemctl --user status nucleated.service --no-pager

Then ask it to check itself. This validates its config, checks that each environment's unit and nucleus exist, and, if the box reports to Watch, sends one heartbeat:

Boxas agent
nucleated check

It names anything that fails. To see what the daemon sees, with or without a Watch account:

Boxas agent
nucleated status

Your environment should be listed with its agent server alive and no sessions yet. nucleated covers the daemon in full, and Connect a box covers Watch.

What you have now #

Open claude.ai/code or the Claude phone app, signed in as the box's account. The box appears there by name, and you can start a session on it. Do not trust it yet.

Next, prove it works.