For AI agents: the complete documentation index is available at https://jig.md/llms.txt, the full documentation bundle is available at https://jig.md/llms-full.txt, and this page is available as Markdown at https://jig.md/index.md.

Jig · Run code and Agents together

Build with Agentsas naturally as youbuild with code.

Invoke Agent reasoning as naturally as ordinary code. Jig runs your methods locally with explicit powers, strict containment, accountable cancellation, and zero license surveillance.

Developer alpha · Linux and Mac hosts · Bread source-available 🍞
A support case arrives

“I was charged twice for my subscription.”

Execute Flow: classify-and-route

  1. Match keywords
  2. Check strict pattern
  3. Fall back safely

Deterministic code: fast, rigid, predictable.

Recognize known regex keywords or flags. Anything ambiguous falls back to manual review. No model call; code rules can still misclassify.

Suggested queuemanual-review
See the caller and implementation

The caller stays the same

return run.call({
  operationId: 'classify-request',
  slot: 'classifier',
  input: run.input,
})

Result

done → { queue: "billing", priority: "high", requires_human: false }

Illustrative walkthrough. Code enforces invariant contracts; Agent judgment interprets human intent. Changing an implementation changes cost and latency, never the caller's interface.

Explore contact import with code and Agents

One method call. Code, an Agent, or both.

Your app needs to route a request. Change the implementation below: your application makes the exact same call regardless of who does the reasoning.

Run the complete example in your terminal

The execution boundary

Let Agents interpret.
Let your code decide.

Prompts are not policy. An Agent can interpret a customer’s nuance, draft an investigation, or propose a code change. But your application code checks records, enforces business rules, and decides the consequences.

Bring your Skills, prompts, and libraries into bounded methods. Code and Agent work share the same callable boundary, defined by the independent FLOW standard. Your application stays in command.

See code check an Agent’s proposal ↗

How applications stay in control

  1. 1. Delegate the reasoningA Flow invokes an Agent to interpret unstructured data.
  2. 2. Enforce domain policyYour code verifies the proposal against strict business invariants.
  3. 3. Authorize the consequenceProceed, request human review, or withhold action.

Checks need domain knowledge. A well-formed answer can still be wrong.

A microkernel for agent-native systems

A small core.
Uncompromising containment.

Methods own the work. Jig handles the execution around them: running reviewed code, granting operator-authorized resource access, and fencing owned work when you cancel. Completion requires confirmed settlement; cancellation is not instantaneous.

This separation lets you build new capabilities without giving models ambient system access. Agents have room to reason inside their methods; their judgment does not grant them more authority, access to raw credentials, or the ability to spawn untracked processes.

Understand the architecture ↗

Jig’s host containment boundary

Your Flow

Code · Agents · Skills · Libraries

The method owns how the work happens.
  • Grants only operator-authorized resources; credentials stay host-owned
  • Enforces strict process, memory, and timeout limits
  • Refuses success when owned cleanup is unconfirmed

Jig governs execution. Your application directs meaning and authority.

Capability compounding

Build the builders.
From one method to a fleet.

A single method solves one task. When methods compose, capability compounds. Each specialist has explicit inputs, outputs, and bounded powers—enabling coordinated multi-agent systems with power under control.

Run one Flow.
Build with confidence.

Create a small project, run a method, and inspect its result in your terminal. The first run uses ordinary code and needs no Agent.

Start building

Developer alpha · Check supported hosts and prerequisites

What to know about this alpha

Jig is Bread source-available, not open source. Personal non-business use and genuine evaluation are free; qualifying business groups below $1M annual revenue also have a free grant. See pricing and the license for terms. FLOW is independently licensed. Agents can hallucinate or follow injected instructions; Jig does not guarantee correct judgment. Harmful decisions within granted authority remain possible. Remote Agents receive the data intentionally sent to them. Cancellation cannot retract accepted remote requests or undo completed effects. Production-scale performance is not established.

Agent choices · Execution guarantees