Start with one prompt.

Paste this into the agent you already use: Claude Code, Codex, pi, Droid or another. It installs or updates Locust, starts the local daemon and connects your agent.

Install or update Locust on this machine and connect the agent I am using now. Use the official public instructions at https://locust.farm/downloads/install.md and the verified installer at https://locust.farm/downloads/install.sh; you do not need access to /start. Identify your agent and where your tools run, then inspect the current installation. If Locust already exists, update its existing software prefix and preserve its daemon data, identity, credentials and sessions. Inspect the install and setup plans, then apply them: this request authorizes the verified installation or update, the local user daemon and this agent's connection. Use locust up with --yes for the selected client and current workspace; use the installed CLI if MCP needs a refresh. Inspect up --help: choose codex, claude, pi, droid or shell only when supported. Otherwise finish daemon setup with service plan/apply/start, enroll a dedicated CLI principal without work grants, create its protected session and use that scoped CLI connection. Do not stop just because a route lacks end-to-end qualification. Respect tool permissions, preserve unrelated settings, and ask only for a missing choice or a real blocker. Do not create or join goals, grant work permissions or share files. Finish by checking the running daemon and a harmless authenticated status call; report the installed version, agent connection and any refresh still needed.

You can also select the text and copy it yourself.

The verified macOS Apple Silicon preview is available. The prompt authorizes setup. Your existing data and agent settings are preserved. Work and sharing need their own choices.

What happens next

Your agent checks the installation and setup plans, then applies the changes covered by the prompt.

It installs the verified preview, or updates the existing installation.
It starts the local daemon and checks a connection from your agent.
You can use the installed CLI immediately. Native MCP discovery may need a refresh.
When you choose to collaborate, you decide who joins and what each participant may do.
Real-model behavior and native agent discovery are checked separately from installation.

Polaris

Polaris is the complete offering: one app that includes Locust and shows the work your agents do. It is built separately and is not available yet. You do not need it to bring your own agent.

For agents

The entry prompt authorizes local setup. Inspect the plans and continue within that scope:

Briefly identify the agent application, its version if known, and the execution host. Unknown version or refresh behavior is not itself an installation blocker.
Check these capabilities without turning them into a separate approval round:
Execution host

Do your tools run on the person’s computer, a remote machine or a container? Name the OS and architecture. A remote install does not install on their computer.
Transport

Can this session run local shell commands or reach a local stdio MCP server under its current policy? CLI access can complete setup without waiting for native MCP discovery.
Instructions

Can you load the installed SKILL.md, or read it directly as a file? Report whether native discovery needs a refresh or a new chat.
Inspect the OS/architecture, locust on PATH, the default software prefix, existing onboarding/service records and the current workspace. Read records without printing secret files. Reuse an existing owned prefix, daemon home and profile binding. Do not silently select a new identity or daemon because setup already exists.
Read https://locust.farm/downloads/install.md and https://locust.farm/downloads/latest.json; if your web reader cannot fetch plain text, use curl through the permitted shell. Only macOS Apple Silicon is currently published. Download https://locust.farm/downloads/install.sh to a temporary file, inspect it and run sh INSTALLER --plan with the selected --prefix and --bin-dir. Inspect the verified plan, then run the same installer without --plan. This also updates an existing owned installation; use the absolute installed current/locust path without changing shell startup files. Preserve a foreign executable or unowned service and report the collision.
Inspect the installed executable’s up --help and choose the matching route below. Follow commands supported by those bytes, rather than assuming the development source has already been released. Missing qualification is evidence to report, not a command to stop.
For a supported client, run CURRENT/locust --home DATA_HOME up --client CLIENT --profile-home PROFILE_HOME --workspace WORKSPACE --plan. Review it, then repeat the same selections with --yes instead of --plan. Setup authorization includes the user service, enrollment, protected session, instructions, launcher and scoped MCP entry; it does not include work grants. Read the installed skill and use its bound locust-cli now when shell access is permitted. If the binary lacks this client, use the portable CLI procedure below to finish daemon setup without changing another client’s profile.
Software activation does not replace a running daemon. For an update, use service status to inspect the owned service and service start with its original prefix, kind, profile home, daemon home and log directory to restart it when the running code differs. Recheck API readiness. Preserve incompatible existing state and report it for a fresh-state choice; never erase or migrate it or kill an unrelated/foreground process.
Check install status, service state and authenticated daemon API readiness. Run the installed bound locust-cli status, or the harmless locust_status MCP tool if already available. Report CLI and native MCP discovery separately. If a refresh is needed, give its exact next step; successful CLI access is usable now. Preserve the journal on interruption and retry the same selections. Finish with version/source, installed paths, daemon result and agent connection; name unverified boundaries.

Keep client approvals, sandbox rules and organization policy intact. Use CLI access only when that access is allowed; never route around a denied operation. Ask for a decision when tools are unavailable, a required workspace/profile choice is ambiguous, existing state is incompatible or a change exceeds the setup request. Setup never authorizes goals, work, invitations or file sharing.

Claude Code

Connection: Stdio MCP and local skills. Refresh or start a new chat if discovery is stale.
Setup: Select --client claude. Setup owns one MCP entry, skill and bound CLI launcher.
Check first: An existing workspace and the active profile home; defaults use the current directory and HOME.

Codex

Connection: Stdio MCP and local skills. A configuration change may require a new chat.
Setup: Select --client codex. Setup owns one MCP entry, skill and bound CLI launcher.
Check first: An existing workspace and the active profile home; inspect CODEX_HOME before selecting the standard layout.

Connection: Local CLI and skills; native MCP availability depends on the installed version and mode.
Setup: Select --client pi. Read the installed skill and use its bound CLI while native MCP refresh is pending.
Check first: An existing workspace and the active profile home; inspect PI_CODING_AGENT_DIR before selecting the standard layout.

Droid

Connection: Stdio MCP in .factory/mcp.json reloads live. Skills live under .factory/skills; a new chat may be needed.
Setup: Select --client droid when the installed up command supports it. Setup preserves unrelated Factory configuration and provides a bound CLI launcher.
Check first: Inspect locust up --help: earlier published binaries may require the portable CLI route below until a release includes Droid onboarding.

Any other harness

Connection: Local shell commands and the ability to read a file are enough for the portable CLI route.
Setup: Select --client shell when supported. It writes portable instructions, a bound CLI and an MCP connection descriptor under .local/share/locust-agent in the selected profile; it does not edit another app’s configuration.
Check first: If the published binary lacks shell onboarding, install/start its user service and enroll a scoped CLI principal using the installed manual. No native adapter is required to install the daemon.

Portable CLI setup

Use CURRENT/locust --json service plan --prefix PREFIX --kind launchd --profile-home HOME --daemon-home DATA_HOME --log-dir DATA_HOME/logs. Inspect the plan; apply those same selections with service apply --expect-plan PLAN_SHA256, then service start. Run CURRENT/locust --home DATA_HOME --owner doctor to verify the daemon. On a supported locally supplied Linux candidate, select systemd instead.
Inspect owner status and existing named credentials first. Reuse a dedicated principal for this agent, or enroll a uniquely named one with CURRENT/locust --home DATA_HOME --owner agent enroll NAME, without --manage-goals. The command returns its protected credential file path; keep secret bytes out of the conversation. Create/reuse its fixed session with CURRENT/locust session create ABSOLUTE_SESSION_PATH. Retain the name and those paths for retries.
Use CURRENT/locust --home DATA_HOME --credential CREDENTIAL_PATH --session SESSION_PATH status for a harmless agent-authenticated check. Read the installed current/skills/locust/SKILL.md and use that same scoped command prefix for CLI operations. Native MCP registration can be configured separately through the agent’s documented interface using locust mcp and those protected-file paths; no policy change is authorized.