Factory Droid

Orutta connects to Factory Droid through its droid executable and Agent Client Protocol mode. Factory owns the account, model routing, credentials, autonomy settings, and provider service; Orutta supplies the task, repository environment, transcript, approvals, review surfaces, and Git workflow around the session.

Install

Use Factory’s official installer:

curl -fsSL https://app.factory.ai/cli | sh

Verify that the executable is available:

droid --version

On Linux, Factory may require xdg-utils for browser-based authentication. Ensure the installer’s binary directory is on PATH in a fresh terminal.

Authenticate

Start Droid interactively:

droid

When prompted, complete Factory’s browser device-pairing flow. For headless use, generate a Factory API key and make it available through:

export FACTORY_API_KEY="fk-..."

Orutta’s ACP integration can use either a device-paired session advertised by Droid or the API-key method. Do not commit the key or paste it into a task transcript.

Verify

From a disposable repository:

droid --version
droid

Confirm that authentication completes and a harmless read-only request succeeds. For API-key verification, test the environment variable in the same shell context that launches Orutta.

Connect to Orutta

Capabilities in Orutta

Factory Droid sessions can expose:

• Model and reasoning-effort options advertised through ACP
• Normal execution and Droid’s spec-oriented plan mode
• Tool calls, command output, file changes, and assistant text
• Permission and autonomy controls supplied by the runtime
• Browser device pairing or FACTORY_API_KEY authentication
• Session configuration negotiated at startup
• Orutta’s terminal, browser, diff, checkpoint, worktree, and Git delivery surfaces

Orutta applies Droid’s model and reasoning choices through ACP session configuration because command-line model flags are not authoritative in every ACP release.

Orutta does not currently classify Factory Droid as supporting native live-turn steering.

Updating

Use Factory’s supported update path or rerun the official installer, then restart Orutta. Orutta can recognize common Droid installations and may expose an update action when the runtime supports it.

Create a new task after an update that changes ACP configuration, model discovery, authentication, or autonomy modes.

Usage credentials

Orutta can read usage limits from available Factory credentials, including supported secure storage. If usage is unavailable, check that the same local Factory account is authenticated; missing usage data does not mean the allowance is zero.

Troubleshooting

Droid is not detected

1. Run droid --version from a fresh terminal.
2. Confirm the installer directory is on PATH.
3. Check Orutta’s custom binary path.
4. Restart Orutta after installation or environment changes.

Device pairing does not complete

Run droid directly and complete the browser flow. On Linux, verify that a browser opener such as xdg-open is available. In headless environments, use FACTORY_API_KEY instead.

The API key is ignored

Confirm that FACTORY_API_KEY is exported in the environment that launches Orutta. An environment variable set in one terminal does not automatically reach an already-running desktop application.

Model or reasoning options are missing

Update Droid, authenticate directly, and start a new Orutta session. The ACP runtime advertises the available configuration for each session.

Official documentation

• Factory Droid quickstart
• Droid CLI reference
• Droid Exec and API-key setup

Continue with Your first task or Provider handoffs.