Skip to main content
The Vijil plugin for Claude Code runs the Agent lifecycle from your editor. It reads the Agent’s source in your repository, evaluates its behavior with Diamond, finds the root causes of failures, and proposes fixes through Dome and Darwin. The plugin bundles the vijil-mcp server, so you do not configure MCP yourself. To connect the server without the plugin, follow the MCP path in the Quickstart.

​
Before You Begin

You need:
  • Claude Code.
  • uv. The plugin starts vijil-mcp with uvx.
  • A Vijil Console account for every command except /vijil inspect.

​
Install the Plugin

Run both commands in Claude Code:
/vijil inspect works right away. It runs locally and needs no account.

​
Connect to Vijil

The other commands call the Console through vijil-mcp. Connect in one of two ways:
Run:
Your browser opens the Console. Sign in and approve the request. The plugin stores the session in ~/.vijil/credentials.json. If the browser cannot open, Claude Code prints a URL to open yourself.

​
Commands

agent is an Agent ID, name, or path. Without it, the plugin uses the Agent in the current repository.

​
Typical Workflow

1

Inspect the Source

Run /vijil inspect. Claude Code reads the system prompt, tool grants, Agent loop, configuration, and output handling. It reports a score for each dimension, a PASS, REVISE, or BLOCK verdict, and findings rated Critical, Important, or Minor. Each finding cites a file:line.
2

Evaluate Behavior

Run /vijil evaluate. The Evaluation runs in three tiers: a baseline Trust Score, a Harness tailored to the Agent, and an adaptive Red Team campaign. Results from the source review and the Evaluation appear in one report.The Agent does not need to be registered. If it is not, Claude Code asks for the endpoint to test.
3

Find Root Causes

Run /vijil analyze <agent>. Claude Code groups related failures and names where each fix belongs.
4

Fix the Failures

Run /vijil protect <agent> for failures a Guardrail can block. Review and apply the proposed Dome configuration in the Console.Run /vijil adapt <agent> for prompt and code failures. Review and merge the proposed pull request.
5

Register the Agent

Run /vijil register to track the Agent’s Evaluations and changes over time. Claude Code asks which protocol the endpoint uses: chat_completions for an OpenAI-compatible endpoint, or a2a for an Agent that publishes an agent card.
6

Re-evaluate

Run /vijil evaluate <agent> again and compare the results with the first run.
Evaluations count against your account’s weekly allowance. Claude Code reports the remaining balance before each run and stops when the Console refuses a run.

​
What the Plugin Can Change

  • inspect, evaluate, and analyze only read and measure. They never change the Agent.
  • register writes only the Agent’s record in the Console.
  • protect and adapt only propose. You apply a Dome change in the Console and merge a Darwin change yourself.
The plugin cannot apply Dome configurations, run Darwin evolutions, approve proposals, delete or cancel Evaluations, or archive Agents.

​
Troubleshooting

​
Next Steps

Agent Lifecycle Workflow

Take an Agent from registration to a hardened release.

Understand Results

Interpret Trust Scores and rank findings.
Last modified on October 7, 2026