Skip to main content

Jarvis CLI

Jarvis is a distributable terminal AI coding agent. Install it from PyPI with pipx or pip, or download a standalone executable from GitHub Releases. Cloning the repository is only required for development.

Current contract line

Jarvis 0.11.0 consumes the provider-neutral Jarvis Core 0.17.0 contracts. Cloud completion is bound to the exact local run ID and requires real passing test records.

Jarvis Core 0.17.0 is published as an immutable PyPI release; the CLI pins that exact release so Jarvis and Core can evolve independently.

Jarvis is a standalone local coding agent. Bare tasks run the agent loop and tools on the user's machine and send model requests directly to jarvis-inference. AI Stack is an optional sibling service for durable remote runs, shared queues, persistence, retrieval, integrations and UI; Jarvis does not require it for local work.

Install

Jarvis is distributed as a normal Python application. You do not need to clone the Git repository to use it.

Python 3.10+ is required. pipx installs Jarvis into an isolated environment and exposes the jarvis command globally.

python3 -m pip install --user pipx
python3 -m pipx ensurepath
pipx install jarvis-agent-cli
jarvis --version

Upgrade later with:

pipx upgrade jarvis-agent-cli

Standard pip

python3 -m pip install jarvis-agent-cli
jarvis --version

Standalone executable

Download the platform-specific jarvis-* executable from GitHub Releases. Releases provide Linux amd64, macOS arm64 and Windows amd64 builds, plus SHA256 checksums and build provenance.

On Linux/macOS:

chmod +x ./jarvis-*
./jarvis-* --version

On Windows, run the .exe directly from PowerShell or Command Prompt.

Development install

Only contributors working on the source tree need a repository checkout:

git clone https://github.com/abdullahalrifat/jarvis.git
cd jarvis
python3 -m pip install -e .

Jarvis 0.11.0 consumes jarvis-agent-core==0.17.0 from PyPI. The dependency is pinned to the exact Core release in pyproject.toml.

See docs/install.md for the complete distribution and upgrade guide.

Token-efficient runtime

Core 0.17.0 provides provider-neutral primitives for bounded context construction, token/cost estimation, route budgets, adaptive routing and empirical route calibration. Jarvis keeps provider-specific execution policy in the CLI, while shared efficiency and calibration contracts remain reusable across local and remote providers without adding provider SDKs to Core.

Context construction can prioritize required task state, recent tool evidence and relevant files under an explicit budget. Route decisions can account for estimated token cost, latency, risk and measured task outcomes.

Real workload efficiency benchmark

Jarvis owns local runtime observations, task-level workload definitions and quality evaluation. AI Stack owns telemetry and calibration for server-side Runs. Both adapt their own measured outcomes to the provider-neutral jarvis-core observation/calibration contract. The benchmark covers CI triage, provider architecture, release readiness, PR review, documentation alignment and efficiency audits.

Use the corpus to compare local-only, automatic and cloud-first routes using success, quality, incorrect completions, tool failures, latency, input/output/cache tokens and estimated cost. Runtime evidence should only influence automatic routing after the Core minimum-sample and quality-floor safeguards are satisfied.

Connect directly to inference

Configure Jarvis to use the dedicated inference gateway. No AI Stack, database, vector store, or web UI is required for local repository work.

export INFERENCE_BASE_URL=http://<inference-vm-ip>:8080/v1
export INFERENCE_API_KEY=<your-inference-secret>
export JARVIS_MODEL=qwen3:1.7b

jarvis model-doctor
cd /path/to/repository
jarvis "review this repository and fix the highest-impact issue"

Bare tasks use the standalone local agent. The agent loop, repository tools, permission checks and verification run on the machine where Jarvis is installed; only model requests go to the inference gateway.

Optional AI Stack integration

Use AI Stack when you need its durable remote Runs API, shared queues, persisted run history, retrieval, integrations or web UI. Configure AI_STACK_BASE_URL and AI_STACK_API_KEY, then make the server boundary explicit:

export AI_STACK_BASE_URL=http://<ai-stack-host>:8081
export AI_STACK_API_KEY=<your-ai-stack-agent-key>
jarvis run "review this repository" --workspace /workspace/repo
jarvis cloud health

jarvis run and jarvis cloud are explicit remote operations; they are not prerequisites for local work. See docs/architecture.md for ownership boundaries and migration details.

Jarvis versus Server

Need Use
Local repository work, interactive terminal, local automation Jarvis
Durable cloud tasks, shared queues and external workers Server

Jarvis and Server share stable contracts through jarvis-agent-core, while tool execution and storage policy remain separate.

Implemented runtime

The runtime includes bounded repository/Git tools, allowlisted command execution, sandbox/network policy, sessions/checkpoints, proof records, multimodal context, hierarchical instructions/memory, Skills/Hooks, deny-by-default MCP, repository/LSP intelligence, worktrees, plan mode, adaptive context, failure memory, multi-agent execution, heterogeneous routing, browser verification, background jobs/cron, observability and the remote Run/cloud worker protocol.

Development

python -m pip install -e . -r requirements.txt
black --check --diff src tests
ruff check src tests --select E9,F63,F7,F82
pytest -q --cov=. --cov-report=term-missing --cov-fail-under=70
python -m build

Additional guides:

Production request path

Normal bare-task usage is Jarvis CLI -> jarvis-inference -> model backend. AI Stack is an optional consumer of the same inference contract.

Metadata

Release files for jarvis-agent-cli 0.11.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for jarvis-agent-cli 0.11.0
File Size Uploaded Provenance Actions
jarvis_agent_cli-0.11.0.tar.gz 171.3 kB With provenance Details for jarvis_agent_cli-0.11.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for jarvis-agent-cli 0.11.0
File Interpreter ABI Platform Actions
jarvis_agent_cli-0.11.0-py3-none-any.whl Python 3 none any Details for jarvis_agent_cli-0.11.0-py3-none-any.whl

Total release size: 339.3 kB

Release files / jarvis_agent_cli-0.11.0.tar.gz

Download URL jarvis_agent_cli-0.11.0.tar.gz
Size 171.3 kB
Tags Source
SHA-256 checksum
How to use checksums
a3824048d18c7de91e4421362215e719e2d58e8d3415aafb447a29e8eb91430b
BLAKE2b-256 checksum
How to use checksums
102ed8a5ae3758d4692b4eb7cd9507c2788683d4571b32ff494c207131050bce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.

Transparency log

Release files / jarvis_agent_cli-0.11.0-py3-none-any.whl

Download URL jarvis_agent_cli-0.11.0-py3-none-any.whl
Size 168.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ad71dcfe5cc05979816666a8159758ed3268ec38894e29fb482f40935f599803
BLAKE2b-256 checksum
How to use checksums
8382eaa691d2124cf253d1e3ccf871a8c21b519ea41317e45d1100eb525b91a6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.

Transparency log

Security for jarvis-agent-cli 0.11.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for jarvis_agent_cli-0.11.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page