Product

Try Intent-System

Intent-System is open source and intent-cli v0.22.0 is released and stable. Herdr-only is the preferred non-preview path for collocated teams; agmsg plus herdr remains supported for distributed or existing-agmsg teams. intent-cli emits guidance and verifies state; your coding agent or operator runs herdr, providers, and schedulers.

Build your first agent team→View on GitHub

Install

v0.22.0 adds a Node/npm path that does not require a .NET SDK. Install the intent-cli command globally with:

npm i -g intent-system

If you prefer not to install globally, npx runs the tool fully and prints one line suggesting the global install; it never installs globally by itself. Verify with intent-cli --version, then open Claude, Codex, Copilot, or any coding agent with access to your repo and say: "ask intent-cli what phase I'm in and what to decide next."

Already using the .NET SDK? The .NET global tool remains available:

dotnet tool install -g JTechJapan.IntentSystem.Cli

Full quickstart & docs on GitHub→How the agent team is wired

Recommended operating model

Ask your agent to build a herdr-only team

Installation is only the first step. The first useful milestone is a four-role workspace whose receiver liveness and end-to-end handoff have been verified.

01
Install intent-cli
v0.22.0 adds the npm entry path, executable-path update channels, guide-first acceptance, and supervision corroboration to the released contracts.
02
Ask in natural language
Say “start this work in a herdr-only team”; the agent asks for the required choices and emits commands for your approval.
03
Receive the ready report
The agent records topology, validates panes and liveness, then reports the first verified handoff.

Design can stay in your current conversation or use its own herdr pane. The other roles receive dedicated panes and folders after the approved setup is run. In herdr-only mode, dispatch and completion use the visible herdr session layer; agmsg plus herdr remains supported for distributed or existing-agmsg teams, and neither transport is primary.

Start this work in a herdr-only four-thread team for <owner>/<repo>.
Use intent-cli's bootstrap guide, ask me for the CLI/model for each seat and the application kind, and emit commands only.
After I approve, I will run herdr, provider, and scheduler commands; record and validate the topology, then report the first verified handoff.

In released v0.22.0, herdr-only is the preferred non-preview path for collocated teams. Use exactly one session transport and one driver per domain/repository; the three-thread timer loop remains a supported simpler alternative. See the alternative →

Current v0.22.0 capabilities

The released contract, in one place

Released baseline

intent-cli v0.22.0 is released and stable. Four-thread orchestration is the primary model regardless of transport; the three-thread timer loop remains a supported alternative, and a domain/repository chooses one driver mode.

v0.22.0 reader entry

The npm channel adds npm i -g intent-system as a global install for the intent-cli command, with no .NET SDK required. npx runs the tool fully without a global install. intent-cli update derives its channel from the executable path.

Acceptance and supervision

Guide primacy is an acceptance rule: a capability whose guide route is missing or wrong is not shipped. Supervision corroborates findings within the cycle before escalation, so healthy sessions are not reported as broken.

Session choices

herdr-only is the preferred, non-preview path for collocated teams. agmsg plus herdr remains supported for distributed teams or teams that already use agmsg; neither transport is primary.

File-backed delivery

Declare delivery_method: file-backed to persist a durable, addressable task envelope and deliver a one-line pointer. Without that declaration, delivery remains inline.

Named branch lanes

A lane comes from the registry/default or an explicit packet draft --lane choice. This is a released preview-through-1.x capability, not a 1.0 compatibility guarantee. The packet records branch_lane and routing_snapshot; intent-cli proposes and records the lane but does not create or manage branches.

Git-backed multi-user claims

claim acquire and claim verify use immutable Git-backed records under .intent-cli/claims/. This is a released preview-through-1.x capability, not a 1.0 compatibility guarantee. Only the successful plain push owns the claim, so claim before scaffold and verify ownership before work proceeds.

Prompt class and scope

Prompt policy uses literal prompt classes and scoped approval, including answerable_by, a hard non-overridable risk floor, and live-dialog compare-and-swap. This is a released preview-through-1.x capability, not a 1.0 compatibility guarantee. Unknown or unmatched cases escalate instead of guessing.

Authoring-only team mode

With team_mode=authoring-only, you can shape intent and publish an issue without writing code. The agent interviews intent and authors packets; implementation may be handled by another team, a human, or a vendor. This mode provides no delivery topology or delivery seats; delivery mode remains the default, and delivery supervision is not applicable in authoring-only mode. This is a released preview-through-1.x capability, not a 1.0 compatibility guarantee.

Command-emitter boundary: intent-cli supplies deterministic guidance and records or verifies workflow state. The coding agent or operator runs herdr, providers, and any scheduler after the relevant decision; intent-cli does not launch them, operate herdr, or register a scheduler.

Authoring-only onboarding

Shape intent and publish an issue without writing code

With team_mode=authoring-only, you can shape intent and publish an issue without writing code. The agent interviews intent and authors packets; implementation may be handled by another team, a human, or a vendor. This mode has no delivery topology or delivery seats; delivery mode remains the default, and delivery supervision is not applicable in authoring-only mode.

Use team_mode=authoring-only for <domain>.
Interview me about intent, author the packet, and ask for approval before publishing the issue.
Do not create delivery topology or seats; report the authoring audit and external handoff.

Community & support

Join the J-Tech Japan OSS Discord for community questions and discussion — answers there are free. File reproducible bugs and actionable feature requests as GitHub issues.

For hands-on adoption — pair programming, pair storming, Intent Storming facilitation against your own codebase — J-Tech Japan offers paid consultation.

Join the Discord→Support & consultation

Learn the methodology

The methodology stands on its own, with or without the tool. The three proposals — Compass, Git-AI-Flow, and Intent Storming — are independent of any product, and you can apply them to your existing toolchain today.