Prima Code CLI

Prima Code is a cross-platform command-line workspace assistant. It gives you an interactive shell for searching, editing, and reasoning inside your repositories with the help of the Prima agent.

Install from npm

``bash
npm install -g @esimplicity/prima-code
`

$3

- macOS, Linux, or Windows (x64 or arm64)
- Node.js 16+ and npm (or use corepack to manage npm versions)
- A Prima governance platform

Quick start

1. Authenticate with npm (if your organization requires it) and install the package globally.
2. Create a config.toml at ~/.prima/config.toml that looks similar to:
`bash
approval_policy = "on-request"
sandbox_mode = "workspace-write"

platform_url = "http://api..com/engine/aiox/"
control_tower_url = "http://api..com/control_tower/"

[model_providers.prima]
name = "OpenAI"
base_url = "http://api..com/engine/aiox/v1"
env_key = "PRIMA_API_KEY"
wire_api = "chat"

[profiles.prima]
model_provider = "prima"
model = "prima-gpt-5"
prima_workspace = "Test Workspace"
`
3. Launch the CLI:
`bash
prima
`
4. Follow the on-screen prompts. Press Ctrl+C to exit.

Updating

To upgrade to the latest published version:

`bash
npm update -g @esimplicity/prima-code
`

Check the current version with:

`bash
prima --version
`

Configuration

- Prima uses the config.toml to load the models and workspaces available via prima.
- Additional settings can be provided through the CLI flags; run prima --help for details.
- Proxy or custom CA environments should configure standard Node.js variables (HTTPS_PROXY, NODE_EXTRA_CA_CERTS, etc.).

Troubleshooting

- Binary not found: Reinstall the package or ensure that your global npm bin directory (e.g., ~/.npm-global/bin) is on PATH.
- Permission errors on install: Use npm config set prefix ~/.npm-global or install via fnm/nvm-managed Node to avoid using sudo.
- 401 or rate limits from Prima: Verify the API key, usage quotas, and network connectivity.

Contributing

Issues and pull requests are welcome. Please use the repository issue tracker to report bugs or request features. When contributing code, run cargo fmt, cargo test, and follow the project’s linting rules described in the codex-rs README and the /codex-cli/scripts` documentation.