This project has been archived by its maintainers, and is no longer receiving any updates.
JARVIS Runtime
This repo contains the Jarvis Agent Runtime: a Python runtime for executing Agent Runtime Protocol-style agent flows using the 3-role loop:
Planner → Tool Executor (arg-gen + invoke) → Chat
It is designed to run against the Tool_Registry service and share contracts via jarvis-model.
Quickstart
See:
docs/quickstart.mddocs/trace.md
Install
From PyPI (once published):
pipx install jarvis-runtime
Pre-release (e.g. 0.1.0a1):
pipx install --pip-args="--pre" jarvis-runtime
Or in a virtualenv:
pip install jarvis-runtime
For --tool-registry inproc, install Tool Registry too:
pip install jarvis-tool-registry
Or install the extra:
pip install "jarvis-runtime[inproc]"
Run against a real Tool Registry service
Terminal A (Tool Registry):
tool-registry
Terminal B (Runtime):
jarvis-runtime demo --tool-registry http --tool-registry-url http://127.0.0.1:8000
OpenAI mode (optional)
This runtime uses the OpenAI Python SDK for Responses parsing + structured outputs. To enable it:
pip install -e ".[openai]"
export OPENAI_API_KEY=...
jarvis-runtime demo --mode openai --tool-registry inproc
Optional model overrides:
JARVIS_MODEL_PLANNERJARVIS_MODEL_TOOL_ARGSJARVIS_MODEL_CHATJARVIS_MODEL_DEFAULT
Validation
Unit tests:
python -m unittest discover -v
Or (if you have pytest installed):
pytest -q
Typecheck (pyright):
pyright -p pyrightconfig.json
Design docs
docs/intro.mddocs/design/overview.md
Repo boundaries
- This repo: flow execution, LLM role orchestration, runtime packaging.
Tool_Registry(separate repo): tool discovery + schemas + invocation routing (+ MCP aggregation).JARVIS/Model(separate repo): shared schemas / data model (and eventually the ARP wire protocol spec).
MVP capabilities + known gaps
Capabilities:
- Stub-mode 3-role loop (Planner → Tool → Chat) with trace JSONL.
- Tool Registry integration via HTTP (and
inprocfor tests/sandboxed environments). - Trace replay: rerun Chat from recorded tool results.
Known gaps:
- No production hardening (auth, multi-tenancy, concurrency controls, streaming, persistence).
- Prompt packs and planning heuristics are MVP-grade; no memory/scheduler/control plane yet.
Release files for jarvis-runtime 0.1.0a5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| jarvis_runtime-0.1.0a5.tar.gz | 20.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jarvis_runtime-0.1.0a5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size:42.4 kB
Release files / jarvis_runtime-0.1.0a5.tar.gz
| Download URL | jarvis_runtime-0.1.0a5.tar.gz |
|---|---|
| Size | 20.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
167b17056d0c969a646c6b665b8ac060c9901286a3f1b53b7d530e87e8b39472
|
|
BLAKE2b-256 checksum How to use checksums |
da947d39c0c0738badb914d89cfe80a9d2897cd86135013d94f81d7bbee54463
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 14, 2025.
Transparency logRelease files / jarvis_runtime-0.1.0a5-py3-none-any.whl
| Download URL | jarvis_runtime-0.1.0a5-py3-none-any.whl |
|---|---|
| Size | 22.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e45dee900a63f9887193e554a33dcab3e098d31e30b5c309e0af6da635763705
|
|
BLAKE2b-256 checksum How to use checksums |
185b1f4ce6cd2572a56a72fd045b8b75e0ab7540e2d8e43d17ba36896eb0e4d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 14, 2025.
Transparency log