@clawdbuilder/jig
One tool manager and a set of plugins for the Pi coding agent: permissions per tool and environment, approvals, secrets and records.
Package details
Install @clawdbuilder/jig from npm and Pi will load the resources declared by the package manifest.
$ pi install npm:@clawdbuilder/jig- Package
@clawdbuilder/jig- Version
0.5.11- Published
- Nov 19, 2026
- Downloads
- 2,986/mo · 1,040/wk
- Author
- clawdbuilder
- License
- MIT
- Types
- extension, skill, theme
- Size
- 6 MB
- Dependencies
- 8 dependencies · 4 peers
Pi manifest JSON
{
"skills": [
"./plugins/*/skills"
],
"themes": [
"./plugins/jig-theme/themes/*.json"
],
"extensions": [
"./plugins/jig-core/index.ts",
"./plugins/jig-sandbox/index.ts",
"./plugins/jig-memory/index.ts",
"./plugins/jig-workflow/index.ts",
"./plugins/jig-agents/index.ts",
"./plugins/jig-git/index.ts",
"./plugins/jig-lens/index.ts",
"./plugins/jig-jira/index.ts",
"./plugins/jig-logs/index.ts",
"./plugins/jig-api/index.ts",
"./plugins/jig-ops/index.ts",
"./plugins/jig-review/index.ts",
"./plugins/jig-mongo/index.ts",
"./plugins/jig-session/index.ts",
"./plugins/jig-theme/index.ts"
]
}Security note
Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.
README
Jig
Rules, approvals and a record for the Pi coding agent.
Jig decides what the agent may do. It asks you before a write, keeps credentials and personal data away from the model, and records every call it allows. It never signs in: the tool that owns a login does (Credential sources).
Install
Jig needs Pi 1.4 or later and Node.js 22.19 or later (Compatibility).
pi install npm:@clawdbuilder/jig
pi
Jig is an ordinary Pi package: it loads in the folder your pi already uses. Inside Pi, type /login to sign in to a
model provider, /jig setup to answer the first questions and /jig doctor to check the result:
Jig doctor · 12 ok · 1 warning · 0 failures · 10 skipped
A separate home with its own jig command is optional: A separate Jig home.
Setup and doctor and Your first hour go further.
How it works
Every tool call is classified and decided against your rules before it runs: a read runs, a write asks, a production write is denied. What comes back is masked, and the call, its approval and its cost are recorded in a local file (Architecture).
What you get
| Area | What it gives you | Plugins |
|---|---|---|
| Safety | One policy for every tool, approvals, secrets, masking, records | core, sandbox |
| Code | Git, pull requests and releases; a browser review; CI and deploy | git, review, ops |
| Systems | Jira, logs, saved API requests and MongoDB | jira, logs, api, mongo |
| Work and memory | Workflows with evidence; ticket notes and recall; a card when the agent closes a ticket | workflow, memory |
| Delegation | Child agents under the same rules, with limits | agents |
| Seeing | Cost, failures and waits; a context breakdown; session state; themes and a footer | lens, session, theme |
All fifteen plugins are built. Every plugin needs jig-core; otherwise they work on their own, and each README is
the specification its code follows. jig-herdr is optional: its Work and Context panels read
jig-session's file and show the session in focus.
Company-specific environments, sign-in services and internal tools live in a private company plugin, never here.
Writing a company plugin and the tested jig-acme example
show how; Plugins is the map of every tool.
Works on
- Linux and WSL2: tested in CI and daily use. macOS: runs, with Seatbelt in the sandbox;
filteredandasknetworking meanoffthere (sandbox). Native Windows: not yet, because of the sandbox. - Agent: Pi 1.4 or later, tested with 1.5.2; Jig is a set of Pi plugins, and other agents are not supported.

A code review in Jig's browser page, in its graphite theme. The file list and diffs are on the left, the summary stays beside them, and Approve is in the header; approval still returns to Pi. This is example data.
What is next
Work with a page behind it, not a promise:
- Measure memory before growing it. jig-memory measures recall on real tickets before any embeddings or a graph (Recall).
- Traces and charts from
jig-lens. An OpenTelemetry export to MLflow, and Datasette charts, are later (Viewers).
Learn more
- Your first hour with Jig: install to your first approval, sandbox check and
/lens. - Architecture: the tool manager, the sandbox boundary and where each plugin fits.
- Permissions: environments, rules and the floor configuration cannot lower.
- Plugins: every tool, its actions and the plugin that owns it.
- Setup and doctor:
/jig setup,/jig doctorand what each finding means.
The longer reading paths page keeps the order through Approvals, Secrets, Writing a company plugin, Decisions, Compatibility and the code maps; the docs index has every page, grouped. Contributing covers the checks and where code goes; Security says how to report a problem; Releases says what a version means. Every push runs the type check, Biome, the docs link check, the test suites and the integration services that have an address.
Jig is released under the MIT licence.