{% extends "base.html" %} {% block title %}Coding Agents{% endblock %} {% block content %}
Hand off this fleet to a coding agent (Claude Code, Codex, Cursor, …) in two steps.
Tenant {{ tenant }}.
A single Markdown playbook, rendered for tenant
{{ tenant }}
with your portal URL and NATS host pre-filled. The agent creates its own venv at
~/.dc-portalctl/venv, installs the
CLI, runs auth login (one browser
approval), and follows the playbook for provisioning, launching (local + SSH),
discovery, invocation, and event streaming.
Paste this into your agent. It will install the CLI, prompt you once to approve in the browser, then take it from there. No manual setup on your side.
Read AGENTS.md in this repo. It describes a Device Connect fleet on tenant {{ tenant }} at {{ portal_url }}.
Set up the dc-portalctl CLI per the playbook (install + auth login), then list the devices.
The browser approval is the one human-in-the-loop step — you'll see a verification
page from dc-portalctl auth login at
{{ portal_url }}/auth/cli/<id>.
Click Approve and the agent is authorized.
For agents that can't run dc-portalctl auth login —
e.g. Cursor MCP servers, GitHub Actions, sandboxes without a browser. Mint a token
here and set it as DEVICE_CONNECT_PORTAL_TOKEN.