Feature 03

Bring your coding agent into the Hal loop

Use Codex, Claude Code, or Pi inside the same PRD-driven loop without rewriting your planning workflow.

Last updated: May 9, 2026 · Reviewed by ReScience Lab

Why it matters

Hal treats the coding agent as the engine, not the workflow. Keep the same PRD, stories, validation, and review trail while using Codex, Claude Code, or Pi.

What are pluggable agent engines in Hal?

Pluggable agent engines mean Hal treats the coding agent as the implementation engine rather than the whole workflow. This site mentions Codex, Claude Code, and Pi as supported engines, while Hal keeps planning, validation, running, reporting, archiving, and review checkpoints consistent.

What breaks when the agent is the workflow

If your process lives inside one agent tool, switching tools means rebuilding habits: prompts, conventions, review expectations, and handoff steps. The workflow becomes coupled to the model or interface.

Hal separates the loop from the engine. The PRD-driven process stays stable while the configured coding agent does the implementation work.

How Hal handles it

Configure the engine, then run the same planning and execution flow.

hal plan "describe the product change"
hal convert
hal validate
hal run

The developer keeps the same checkpoints: plan, validate, run, inspect.

What the developer gets

How to review the setup

Check the current Hal configuration, confirm the selected engine is documented in the repo, and run a small loop before handing over a larger feature. Treat engine changes like any other workflow change: test them before trusting them.

What Hal does and does not do

Hal doesHal does not do
Structures PRD-native coding loops around planning, validation, implementation, reporting, and reviewable state.Guarantee code quality, passing tests, delivery speed, revenue, rankings, or production readiness.
Helps supported engines work against smaller, reviewable units of work.Replace developer review, QA, security review, or merge judgment.

Sources and verification

Before adopting this workflow, verify the current Hal source repository, install docs, pricing status, and machine-readable pricing. Check release notes and engine support before relying on Hal in production work.

FAQ

Short answers before you put this into an agent workflow.

Which engines does this site claim Hal supports?

This site mentions Codex, Claude Code, and Pi as supported agent engines. Do not assume support for other engines unless the source repository documents it.

Can I switch engines for a project?

Hal is designed around a pluggable engine workflow, but developers should verify the current configuration and source documentation before relying on an engine for production work.

Does the engine change the review process?

No. Regardless of engine, Hal is built around reviewable state and developer inspection before merge.

Related features

Keep exploring the pieces of a reviewable coding loop.