JARVIS / DOCUMENTATION

Web research and coding tools

Explore a codebase, investigate a failure, research sources and create useful artifacts.

How it fits into your day

Some requests need a chain of work: read the project, understand the failure, inspect a source, make a careful edit and check the result. The high-level agent brings file, terminal, web and delegation tools to those longer tasks.

Configure the task model

Choose a supported provider and its credentials. A local model server must be installed and running separately.

PowerShell / source reference
uv run jarvis model

Prepare the project runtime

Install the dependencies, test runner and command-line tools needed by the project being worked on. Jarvis uses the environment you supply.

Connect diagnostics

The VS Code adapter exposes supported context and diagnostics. Python language checks require an installed ty, pyright or mypy backend.

PowerShell / source reference
uv run jarvis desktop setup-editor --install

Scope and availability

Access follows configuration. Tool permissions, agent profiles and the available environment determine what can run. A skill or requested outcome does not grant credentials or bypass access rules.

Separate stages of delivery. Editing, testing, committing, publishing and deploying are separate actions. A successful local check does not establish that a remote deployment or account operation worked.

A practical first request

The error is visible but its cause crosses several files.

Try: “Read this project, reproduce the failing test, and fix the smallest relevant part.”

A local change with specific validation evidence if the environment supports it. A plausible explanation alone is not a passing test.