Jack HamiltonandGitHub
9e7366fc05
* fix: close KnowledgeStore connections in connectors_router endpoints KnowledgeStore opens a persistent SQLite connection in __init__ but was never closed at the three instantiation sites in connectors_router.py, leaking one file descriptor (plus its WAL handle) per call. The worst offender is _connector_summary(), which is invoked per-connector on every GET /connectors poll from the frontend — after ~100 polls the backend hits the default macOS per-process FD limit (256) and asyncio's accept() starts failing with OSError: [Errno 24] Too many open files. Add __enter__/__exit__ to KnowledgeStore (close() already existed) and wrap all three instantiation sites in `with` blocks so the connection is released deterministically when the scope exits. - connectors/store.py: add context manager protocol - server/connectors_router.py: use `with KnowledgeStore() as store:` in _connector_summary, _ingest, and _run_sync * test: cover KnowledgeStore context manager + connectors_router close leak - test_store.py: add two tests for the new __enter__/__exit__ protocol verifying the connection closes on normal exit and on exceptions. - test_connectors_router.py: add a regression test that monkeypatches KnowledgeStore.close to count invocations and asserts every store opened by GET /v1/connectors is paired with a close. Also fix a pre-existing bug in the test_connectors_router fixture: the router is created with prefix="/v1/connectors" internally (line 92 of connectors_router.py), and the fixture was wrapping it again with prefix="/v1", producing "/v1/v1/connectors". All 6 existing router tests were failing with 404 before this fix. 5 of them now pass; the remaining failure (test_trigger_sync) is an unrelated KeyError on a missing response field and is out of scope for this PR. * test: drop connectors_router regression test — skipped in CI anyway The regression test added in the previous commit relies on FastAPI being importable, but CI's dev-extra install does not include fastapi (it lives in the `server` optional group). All tests in test_connectors_router.py silently skip on CI with "fastapi not installed", so the regression test would never actually execute there. Revert test_connectors_router.py to the upstream main version. The fixture bug I fixed (double prefix) and the connection-leak regression test both deserve a separate PR scoped to test infrastructure — that PR should either add fastapi to dev deps, split server tests into their own CI job, or both. The KnowledgeStore context manager tests in test_store.py are kept because they have no fastapi dependency and will run in CI.
Personal AI, On Personal Devices.
Why OpenJarvis?
Personal AI agents are exploding in popularity, but nearly all of them still route intelligence through cloud APIs. Your "personal" AI continues to depend on someone else's server. At the same time, our Intelligence Per Watt research showed that local language models already handle 88.7% of single-turn chat and reasoning queries, with intelligence efficiency improving 5.3× from 2023 to 2025. The models and hardware are increasingly ready. What has been missing is the software stack to make local-first personal AI practical.
OpenJarvis is that stack. It is an opinionated framework for local-first personal AI, built around three core ideas: shared primitives for building on-device agents; evaluations that treat energy, FLOPs, latency, and dollar cost as first-class constraints alongside accuracy; and a learning loop that improves models using local trace data. The goal is simple: make it possible to build personal AI agents that run locally by default, calling the cloud only when truly necessary. OpenJarvis aims to be both a research platform and a production foundation for local AI, in the spirit of PyTorch.
Installation
curl -fsSL https://openjarvis.ai/install.sh | bash
That's it. The installer handles everything: uv, the Python venv, Ollama, and pulling a small starter model. About 3 minutes on a typical broadband connection. Then:
jarvis
The Rust extension and bigger models continue downloading in the background while you chat. Run jarvis doctor to see status.
Platforms: macOS (Intel + Apple Silicon), Linux, WSL2 on Windows.
Manual install / contributors: see docs/getting-started/install.md.
Quick Start
curl -fsSL https://openjarvis.ai/install.sh | bash
jarvis
jarvis init --preset <name> switches to a starter config. Available presets: morning-digest-mac, morning-digest-linux, morning-digest-minimal, deep-research, code-assistant, scheduled-monitor, chat-simple.
Starter Configs
Install any preset with one command:
uv run jarvis init --preset morning-digest-mac # or any preset below
Prefix every
jarvis ...invocation withuv run, or activate the venv first (source .venv/bin/activate) so plainjarvis ...works for the rest of your shell session.
| Preset | Use Case | What it does |
|---|---|---|
morning-digest-mac |
Daily Briefing (Mac) | Spoken briefing from email, calendar, health, news with Jarvis voice |
morning-digest-linux |
Daily Briefing (Linux) | Same, with vLLM support for GPU servers |
morning-digest-minimal |
Daily Briefing (minimal) | Just Gmail + Calendar, runs on any machine |
deep-research |
Research Assistant | Multi-hop research across indexed docs with citations |
code-assistant |
Code Companion | Agent with code execution, file I/O, and shell access |
scheduled-monitor |
Persistent Monitor | Stateful agent that runs on a schedule with memory |
chat-simple |
Simple Chat | Lightweight conversation, no tools needed |
# Example: Morning Digest on Mac
uv run jarvis init --preset morning-digest-mac
uv run jarvis connect gdrive # one OAuth flow covers Gmail, Calendar, Tasks
uv run jarvis digest --fresh # generate and play your first briefing
# Example: Deep Research
uv run jarvis init --preset deep-research
uv run jarvis memory index ./docs/ # requires the Rust extension — see Setup above
uv run jarvis ask "Summarize all emails about Project X"
Skills
Skills teach agents how to better use tools and improve their reasoning. Every skill is a tool — agents discover them from a catalog and invoke them on demand.
# Install skills from public sources
jarvis skill install hermes:arxiv
jarvis skill sync hermes --category research
# Use skills with any agent
jarvis ask "Use the code-explainer skill to explain this Python code: for i in range(5): print(i*2)"
# Optimize skills from your trace history
jarvis optimize skills --policy dspy
# Benchmark the impact
jarvis bench skills --max-samples 5 --seeds 42
Import from Hermes Agent (~150 skills), OpenClaw (~13,700 community skills), or any GitHub repo. Skills follow the agentskills.io open standard.
See the Skills User Guide and Skills Tutorial for details.
Built-in Agents
| Agent | Type | What it does |
|---|---|---|
morning_digest |
Scheduled | Daily briefing from email, calendar, health, news — with TTS audio |
deep_research |
On-demand | Multi-hop research with citations across web and local docs |
monitor_operative |
Continuous | Long-horizon monitoring with memory, compression, and retrieval |
orchestrator |
On-demand | Multi-turn reasoning with automatic tool selection |
native_react |
On-demand | ReAct (Thought-Action-Observation) loop agent |
operative |
Continuous | Persistent autonomous agent with state management |
native_openhands |
On-demand | CodeAct — generates and executes Python code |
simple |
On-demand | Single-turn chat, no tools |
See the User Guide and Tutorials for detailed setup instructions.
Full documentation — including Docker deployment, cloud engines, development setup, and tutorials — at open-jarvis.github.io/OpenJarvis.
Contributing
We welcome contributions! See the Contributing Guide for incentives, contribution types, and the PR process.
Quick start for contributors:
git clone https://github.com/open-jarvis/OpenJarvis.git
cd OpenJarvis
uv sync --extra dev
uv run pre-commit install
uv run pytest tests/ -v
Browse the Roadmap for areas where help is needed. Comment "take" on any issue to get auto-assigned.
About
OpenJarvis is part of Intelligence Per Watt, a research initiative studying the efficiency of on-device AI systems. The project is developed at Hazy Research and the Scaling Intelligence Lab at Stanford SAIL.
Sponsors
Laude Institute • Stanford Marlowe • Google Cloud Platform • Lambda Labs • Ollama • IBM Research • Stanford HAI
Citation
@misc{saadfalcon2026openjarvis,
title={OpenJarvis: Personal AI, On Personal Devices},
author={Jon Saad-Falcon and Avanika Narayan and Herumb Shandilya and Hakki Orhun Akengin and Robby Manihani and Gabriel Bo and John Hennessy and Christopher R\'{e} and Azalia Mirhoseini},
year={2026},
howpublished={\url{https://scalingintelligence.stanford.edu/blogs/openjarvis/}},
}