Repository navigation
Releases
Releases · mutagent-io/unsupervised
unsupervised v0.1.1
unsupervised v0.1.1
Added
- Software Factory:
references/factory.mdcovers choosing local or Cloud mode
(the user's own session vs Mutagent Cloud's sandboxes), linking a GitHub
Project board and repositories during onboarding, whatfactory.yamlholds
(board, repositories, label roles, merge preset, autonomy), running work
locally (/sync,/spec->/publish->/dispatch,/execute) and on
Cloud (architech factorypush, enable, runs), following runs, relaying
gates and escalations, common failures, and the safety rules: the agent
never adds or removes a person's label, never approves a gate, never merges.
Its CLI isarchitech factory, notmutagent factory(the Agent Factory).
SKILL.md points to it, and the description and trigger cases cover it. - The description rules out the Agent Factory (
mutagent factory), so a
request about it no longer loads this skill.
Changed
- README rewritten around the Software Factory: what you get, how it runs
locally or on Mutagent Cloud, the install lines, and what stays yours.
Fixed
/executeis described as it works: it plans, builds, has the pull request
reviewed, then merges as your merge rules allow, so in Fast Mode the merge is
what you approve. Agents tell the user before they start it and relay its
merge question, andscripts/run-headless.shrefuses an/executeprompt
as it refuses/ship.- The label table:
merge:holdstops work whoever adds it.runs approve --request-changes(in--help, not yet in the docs) is listed with the
other user-only approval commands. The README says onboarding commits two
files. plugin.jsondeclares"skills": ["./"], which older Claude Code releases
accept (a bare"."was refused).- The Release workflow publishes only after Validate passed on the same
commit; a manual release needs a passing Validate run on the tag's commit. - CI pins the Claude Code version used for
claude plugin validate.
unsupervised v0.1.0
unsupervised v0.1.0
Added
- Harness-neutral: works from any agent harness that can read files and run
shell commands, in three phases (start, setup, operate), with capability
checks, a short per-host table, and fallbacks without tmux or without a
shell.AGENTS.mdand a README "For agents" section point other harnesses
to the same steps. - First release: install Architech with the public installer, onboard a
repository, choose a flow (Full-Loop or Fast Mode), and hand work to
Architech from Claude Code or Codex, headless (scripts/run-headless.sh) or
in a background tmux session that can ask questions. - Background and detached runs start a private tmux server with
-f /dev/null,
so none of the user's tmux config (session restore or autosave plugins) runs
in it. The runner is always called by its absolute path in the skill folder. - A run stopped from outside (its process group got a signal) is graded
INTERRUPTED, notFAILED; dispatch.md shows how to stop a run that is
still going by its recorded group. - Where to find the skill's folder when a harness shows it only by name or URI,
without searching the home folder or re-typing the runner. - Write or commit questions, and a choice of how to land a change, are relayed
to the user like plan and merge questions. run-headless.shwritespgid.txt, so a run whose runner was killed outright
(no verdict, runner gone) can be stopped exactly; the docs cover that outcome.run-headless.shstops Architech and writesINTERRUPTEDwhen it is itself
stopped, refuses a/shipprompt, and is meant to run in the background.- Background sessions run on their own tmux server (
-L unsupervised) with
exact targets. - Checked against Architech 0.1.49. On macOS: headless runs cannot ask and end
BLOCKEDwhen they need a decision; a background tmux session shows a
question as a menu the calling agent can answer; journeys in Claude Code and
in Codex ended with a headless run that pushed an unmerged branch. Codex's
default sandbox asks you to approve eachtmux -L unsupervisedcall,
architech update --checkandpgrep, and in one test it answered two
approval questions itself, which the relay rules above now forbid. On Linux:
a clean install,doctor --strictand the offline test suites passed on
Ubuntu 24.04 arm64, with no model run yet. Linux x64 and other harnesses are
expected to work, not yet tested.