ork 0.12.0

Teams that staff themselves and improve the project on their own, with you holding every gate.

Team manager

Spawn a manager from the team pane and tell it what the project needs: "coordinator, four engineers, two QA, one cloud, one LGPD, one fintech". It reads the repo, designs the smallest team the demand actually needs, with a name, an agent and a project-tailored standing role per member, and staffs it through new orchestration tools: ork_project_info, ork_spawn_member, ork_configure_member, ork_disband_member.

Every mutating call stops at a root approval dialog in Ork before anything happens. No answer within two minutes counts as denied. The manager treats a denial as a decision, not an error.

Autopilot

A per-team toggle in the team pane. On a configurable cycle (default 30 min) the coordinator is asked to review the project and file improvement proposals, one file each, under the team's proposals/ dir. They surface in the team pane with approve and reject buttons:

• Approve: the coordinator decomposes it into board tasks and the normal review and PR gates apply.
• Reject: archived and recorded in learnings.md, never proposed again.

Cycles pause automatically while the 5h claude token window is above a configurable ceiling (Settings), so an unattended team cannot burn through a rate window. learnings.md persists what cycles discover, and every briefing points at it.

Messages are never cut

The 1200 char cap used to bounce long agent messages back for re-summarizing. Now the full text lands in the team's artifacts/ dir and the recipient gets the path: nothing is lost, no round trip is wasted, and the PTY injection stays small. The protocol also tells members to take technical questions straight to the teammate who owns the code, not through the coordinator.

Install and update

The update button in the sidebar footer swaps the app in place, or:

curl -fsSL https://raw.githubusercontent.com/rodrigooler/ork/main/install.sh | sh