> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qredence.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Terminal interface

> Use the pinned Prime Agent engine from the terminal alongside the Fleet Prime Agent web workspace.

The web workspace is Fleet's product surface, but the pinned engine remains fully usable from the terminal.

## prime-agent

If you have `prime-agent` installed, launch it as usual:

```bash theme={null}
prime-agent
```

Fleet does not replace or shadow an existing `prime-agent` binary. Both share `~/.prime/agent/`: provider credentials, settings, the managed kernel venv, and logs. Sign in once with `/login` and both surfaces are authenticated.

## fleet-agent agent

The Fleet launcher can also run the pinned engine CLI directly, without a separate `prime-agent` install:

```bash theme={null}
fleet-agent agent <args>
```

This resolves the engine bundle from Fleet's pinned `prime-agent` dependency and forwards all arguments to it. Use it when you want to be certain you are running exactly the engine version Fleet is pinned to.

## When to use which

* **Web workspace** (`fleet-agent`) — multi-project session management, tool cards, attachments, and browsing the workspace tree.
* **Terminal** (`prime-agent` or `fleet-agent agent`) — quick one-off runs, environments without a browser, or engine features ahead of Fleet's pinned version (when using a newer standalone `prime-agent`).

For the engine's own CLI flags, slash commands, and TUI behavior, see the [upstream Prime Agent documentation](https://github.com/PrimeIntellect-ai/prime-agent#readme).