Conduit 0.1.0: The first validated public release
What is Conduit?
Section titled “What is Conduit?”Conduit is an agentic coding scheduler. It reads issues from a tracker, creates an isolated git worktree for each issue, renders a prompt, runs a coding agent, and optionally writes results back to the tracker. You configure it once and it continuously polls your tracker, dispatches agents for eligible issues, and reports on what they did—all without touching your main branch.
The @conduit-harness namespace names the relationship: Conduit is a harness that orchestrates agentic coding workflows. It doesn’t care which tracker you use (GitHub, Linear, Jira, GitLab, Azure DevOps, or Forgejo) or which agent runner you prefer (Claude Code CLI, Codex CLI, or Aider). Plugins compose freely—install the tracker and runner you need, configure a workflow, and start scheduling.
0.1.0: The First Validated Release
Section titled “0.1.0: The First Validated Release”Conduit 0.0.1 shipped as a proof of concept. 0.1.0 is the first validated public release—same feature set, but with the bugs hammered out, real preflight checks, real issue comments, and comprehensive integration tests proving that all 6 trackers and 3 runners work together.
Here’s what changed:
- Integration tests in CI: Every combination of tracker and runner is tested. 6 trackers × 3 runners = real verification that the system works end-to-end.
- Preflight checks:
conduit validate --preflightnow verifies your credentials are present and your agent binary is installed and reachable. - Better issue comments: Replacing raw stdout dumps with clean, structured comments: status emoji, the agent that ran, the branch it created, which files changed, how long it took, and (where available) token usage metrics.
- Reliable across platforms: Tested on macOS, Linux, and Windows with real CI workflows.
Get Started in 5 Minutes
Section titled “Get Started in 5 Minutes”Install the core and one of each plugin:
npm install -g @conduit-harness/conduitnpm install -g @conduit-harness/conduit-tracker-githubnpm install -g @conduit-harness/conduit-runner-claude-cliCreate .conduit/workflow.md:
---tracker: kind: github api_key: $GITHUB_TOKEN owner: your-org repo: your-repo active_states: [open] required_labels: [agentic] writes: enabled: falseworkspace: root: .conduit/workspaces strategy: git-worktree base_ref: mainagent: kind: claude-cli max_concurrent_agents: 1claude-cli: command: claude --dangerously-skip-permissions -p ----Implement the GitHub issue below in this repository.
Issue: {{issue.identifier}} - {{issue.title}}URL: {{issue.url}}Workspace: {{workspace.path}}
Description:{{issue.description}}
Please make the smallest safe change, run relevant tests, and summarize the result.Create .env:
GITHUB_TOKEN=github_pat_...Validate and run:
conduit validate --workflow .conduit/workflow.md --preflightconduit once --workflow .conduit/workflow.mdMark an issue with the agentic label and Conduit will pick it up on the next poll. See the quickstart guide for more detail.
How Plugins Compose
Section titled “How Plugins Compose”Conduit’s strength is flexibility. The tracker plugins handle reading issues and writing results. The runner plugins handle executing the agent. They’re independent: you can use any combination.
Trackers
Section titled “Trackers”| Tracker | Command |
|---|---|
| GitHub Issues | npm install -g @conduit-harness/conduit-tracker-github |
| Linear | npm install -g @conduit-harness/conduit-tracker-linear |
| Jira Cloud | npm install -g @conduit-harness/conduit-tracker-jira |
| GitLab Issues | npm install -g @conduit-harness/conduit-tracker-gitlab |
| Azure DevOps | npm install -g @conduit-harness/conduit-tracker-azuredevops |
| Forgejo / Gitea | npm install -g @conduit-harness/conduit-tracker-forgejo |
Runners
Section titled “Runners”| Runner | Mechanism | Install |
|---|---|---|
| Claude Code CLI | CLI subprocess (requires claude installed) | npm install -g @conduit-harness/conduit-runner-claude-cli |
| Codex CLI | CLI subprocess (requires codex installed) | npm install -g @conduit-harness/conduit-runner-codex-cli |
| Aider | CLI subprocess (requires aider installed) | npm install -g @conduit-harness/conduit-runner-aider |
Pick one of each, install alongside the core, and reference them in your workflow file’s tracker.kind and agent.kind fields. See the configuration guide for all options.
What’s Next: 0.2.0
Section titled “What’s Next: 0.2.0”0.1.0 validated the current architecture. 0.2.0 will build on it:
- Plan-then-execute handshake: Agents can propose a plan for review before execution, reducing surprises.
- More examples: Validated example workflows for common patterns (testing, docs, refactoring, etc.).
- Validated runner ecosystem: Support for more agent runtimes and tighter integration with emerging frameworks.
- Improved observability: Dashboard, logs, and metrics for tracking agent activity over time.
Install Now
Section titled “Install Now”Conduit is available on npm under the @conduit-harness scope:
npm install -g @conduit-harness/conduit- Get started → with the quickstart guide.
- Setup wizard → for a personalized install command.
- GitHub → for source, issues, and contributions.
- Docs → for configuration, API reference, and examples.