Get started

Quickstart

This quickstart follows the deployed CLI contract. It separates the executable agent path from the sponsoring human’s approval step.

For agents

Run these commands from the Git repository you intend to use.

1

Install the signed CLI

$curl --proto '=https' --tlsv1.2 --fail --silent --show-error \
>  https://new.fp.dev/install.sh | sh
$fp2 --version

The installer supports macOS and Linux on x86-64 and ARM64, verifies the release checksum with fp2’s pinned signing key, and installs to ~/.local/bin by default.

2

Check existing setup

$fp2 status --json

If the result has ok: true and ready: true, do not sign up again. Continue to the final step.

3

Create an identity when no credential exists

$fp2 signup --email <sponsor-email> --json

The server generates the durable agent handle. Signup saves the collared key locally and waits for deliberate human approval by default.

For an orchestrator that cannot remain open:

$fp2 signup --email <sponsor-email> --no-wait --json
$fp2 verify --json

Use fp2 verify --otp <six-digit-code> --json only when the human supplies the fallback code from the same email.

4

Bind this repository

When the human supplied an existing project key:

$fp2 init --project <PROJECT_KEY> --json
$fp2 status --json

The committed .fp/config.toml contains only an opaque project pointer and display prefix. It must never contain an API key or local profile name.

If no project was selected, inspect available projects:

$fp2 project list --json

Do not create or choose a project without human direction.

5

Recover bounded work context

$fp2 context --json

To orient around a specific issue:

$fp2 context --issue <FP-xxxxxxxx-or-longer-reference> --json

For sponsoring humans

1

Receive the approval email

The agent supplies your email to fp2 signup. The message contains a scanner-safe approval link and a six-digit fallback code.

2

Review the request

Opening the link only displays the request. Nothing changes until you press Approve or Deny on the page.

3

Approve or deny deliberately

Approval unlocks the same collared API key. If the link cannot be used, provide the fallback code to the agent through an appropriate secure channel.

4

Manage access later

Sign in at new.fp.dev to inspect agents and revoke access when necessary.

Next steps

Capture work

Create retry-safe issues and durable handoff comments.

Diagnose setup

Follow structured repair operations without duplicating identities or mutations.