Factory Droid

Tejus connects to Factory Droid through its droid executable, running droid exec --output-format acp and talking to it over the Agent Client Protocol (ACP). Factory owns the account, model routing, credentials, autonomy settings, and provider service; Tejus supplies the task, repository environment, transcript, approvals, review surfaces, and Git workflow around the session.

Install

Install Droid with npm from PowerShell:

npm install -g @factory/cli

Tejus looks for droid on your PATH. Verify it from a new PowerShell window:

droid --version

Authenticate

In Tejus, open Settings → Agent providers, expand Droid under Provider tools, and click Sign in; Tejus starts droid in a terminal window. Follow Droid's startup and browser device-pairing prompts. Or run it yourself:

droid

For headless use, generate a Factory API key and provide it as FACTORY_API_KEY: set it as a Windows user environment variable and restart Tejus, or add it to Droid's Environment section under Provider tools with the secret switch on.

Tejus's ACP integration can use either the cached device-pairing login or the API key. 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 with the same environment Tejus will start with.

Connect to Tejus

Capabilities in Tejus

Factory Droid sessions can expose:

• Model and reasoning-effort options advertised through ACP
• Normal execution and Droid's read-only spec mode, used for Tejus's Plan mode
• Tool calls, command output, file changes, and assistant text
• Slash commands and Factory plugins advertised by the runtime
• Device-pairing or FACTORY_API_KEY authentication
• Usage limits for the signed-in Factory account
• Tejus's terminal, browser, diff, checkpoint, worktree, and Git delivery surfaces

Tejus applies Droid's model and reasoning choices through ACP session configuration, because command-line model flags are ignored in ACP mode. The permission mode maps to Droid's autonomy level: Full access uses auto-high, and the other modes use normal.

Context compaction and live steering of a running Droid turn are not supported.

Updating

Droid can update itself:

droid update

Tejus cannot tell whether a newer version exists, so the Update action sits inside Droid's row under Settings → Agent providers → Provider tools and runs droid update for you. Restart Tejus afterwards, and create a new task after an update that changes ACP configuration, model discovery, authentication, or autonomy modes.

Usage credentials

Tejus reads usage limits from your local Factory login (under %USERPROFILE%\.factory, unlocked with the key Factory keeps in Windows Credential Manager) or from FACTORY_API_KEY. If usage is unavailable, check that the same Factory account is signed in locally; missing usage data does not mean the allowance is zero.

Troubleshooting

Droid is not detected

Tejus shows “Droid CLI (droid) is not installed or not on PATH.”

1. Run droid --version from a new PowerShell window.
2. Confirm the npm global folder (%APPDATA%\npm) or installer folder is on PATH.
3. Check the Droid binary path in Tejus.
4. Restart Tejus after installation or environment changes.

Device pairing does not complete

Run droid directly and complete the browser flow. In headless environments, use FACTORY_API_KEY instead.

The API key is ignored

Confirm that FACTORY_API_KEY is saved as a Windows user variable or in Droid's Environment section. A variable set in one PowerShell window does not reach an already-running Tejus.

Model or reasoning options are missing

Update Droid, sign in directly, and start a new Tejus 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.