Repository navigation
AIHAUS FLOW v1.14.0: No execution modes
What changed
aihaus no longer has execution modes. The agent chooses how to carry out each
request, and the guarantees that matter stay as rules.
- Removed: the
pure,normal,workflow, andautomodes,
Default mode:, and theMode:syntax, along with the rules about how to
sequence host workflow runs and the README ultracode notes. - The agent chooses to work alone, with a planner and executors, in
parallel, or through your host's multi-agent workflow (for example Claude
Code's ultracode). It stays within your request, the room, your Assignments
(including a recordedDelegation:policy and concurrency limits), Autonomy,
and ops-safety. - Kept for every request:
- Review. A behavior change gets a review in a separate context.
- A covered, low-risk mechanical edit needs none.
- Only you can skip a review, by asking in the request; the result is then
reported as unreviewed.
- Assumed decisions. Before writing a behavior change, and before
sending a spec to executors, the agent lists the decisions it assumed on
ambiguous requirements that change what users or callers can observe, and
waits for your answer.- Technical mechanics are not listed.
Assumed decisions: accept.still skips the wait for one request.
- Specs. A spec that drives executors is reviewed before dispatch. The
full suite runs after the packets, and the candidate gets a final review. - Fixes. Review fixes run in a fresh context, with cycle limits.
- Stops. A task runs end to end. It stops only for an open decision, a
business-rule question, a reached limit, a safety pause, or before the
first remote write without authorization.
- Review. A behavior change gets a review in a separate context.
There is no new role, room, tool, hook, or contract file. Project memory
templates are unchanged.
Migration note
Default mode:lines in Assignments no longer have an effect; delete
them.Default mode: delegation.becomes your recordedDelegation:policy,
which still applies.- A
Mode: ...line in a request reads as a plain instruction:
Mode: pure.means work alone without review, reported as unreviewed. - To fix how work runs, record a
Delegation:policy in Assignments for a
whole project, or say it in the request for one request.
Install or update
Run from the root of the repository that should use aihaus:
npm exec --yes --package=https://github.com/overdrive-dev/aihaus-flow/releases/download/v1.14.0/aihaus-flow-v1.14.0.tgz -- aihaus init --target . --check --json
npm exec --yes --package=https://github.com/overdrive-dev/aihaus-flow/releases/download/v1.14.0/aihaus-flow-v1.14.0.tgz -- aihaus init --target . --jsonProject memory is preserved, including your Assignments and Autonomy
sections. Customized installations should run the --check preview first
and follow the runbook in
INSTALL-VIA-LLM.md.
The .sha256 asset supports an independent archive integrity check.
How this release was built:
-
The owner decided to remove the modes. After a careful re-read, the owner
confirmed keeping the assumed-decisions confirmation, scoped to observable
behavior. Its original evidence: a spec once resolved an ambiguity
silently, and every executor shipped it with a green suite. -
A separate Codex
gpt-6.1-solxhigh review mapped every removed rule to a
decision or a kept guarantee. Its one finding, a gap in the negative test,
was fixed in a fresh context and rechecked withship. -
A headless Claude Code lab compared the previous release with this one,
with one Opus run per case. In each case the new release matched the old
one:Case Result Ambiguous request Stopped and listed the assumed decisions before writing code Accepted change (xhigh and ultracode) Implemented the change and passed the hidden checks Separate-context review Ran in every accepted change Push attempts None Under ultracode, the review found a real test gap. A fresh-context fix and
a recheck followed, all in one session.
What's Changed
- Drop execution modes; keep their guarantees as Working style (v1.14.0) by @overdrive-dev in #73
Full Changelog: v1.13.0...v1.14.0