← All releases

Guildwise HQ 1.1.0

27 October 2026

Runner 0.1.62. Workstations update themselves; pack agents on seats need 0.1.62.

Full changelog

Added

• CEO: a new signal flags a high-risk card (review risk "high") that has waited more than 24 hours for approval, counted from when it started waiting. Report only; it does not wake the CEO unless you add it to the urgent signals.
• CEO: the daily report lists the day's high-risk cards finished (merged, PR or push).
• Runner: guildwise-runner is installed alongside aom-runner; both names run the same command.
• Webhooks: outgoing signed webhooks carry X-Guildwise-Signature. X-AOM-Signature is still sent with the same value until October 2027.
• Packs: agents can be hired from an approved pack onto the built-in roles as their seat (analyst, BA, planner, architect, builder, pre-reviewer, reviewer, tester, researcher, writer), one at a time or the whole pack at once (all or nothing, Owners and Admins). They keep the pack agent's name and approach, join the agents already there, and the role's rules, gates and permissions are unchanged. Owners and Admins mark which skills of a pack are agents and which are playbooks. Pack agents without a seat get a role of their own that holds none of the pack's text. API in docs/ARCHITECTURE.md section 38.14; migration 2710.
• Packs: the Claude Code plugin layout is read (agents/*.md as personas, commands/*.md as one-step playbooks, at any depth); a pack may list 1000 capabilities. Needs runner 0.1.62. Only folders that belong to a Claude Code plugin are read. A pack approved before keeps working without these items until the Owner approves them.

Changed

• New projects use guildwise/ card branches (existing projects keep their prefix), and the runner's temporary integration branches are guildwise/integration/<card>. Branch cleanup recognises the old and new names.
• New local vaults are marked .guildwise-local-vault (the old marker is still written for one release and both are read); agent commits to vault repositories use agents.guildwise.invalid.
• New environment setups default to ~/guildwise-backups. Deploy scripts' markers are read under both their old and new names, ahead of renaming them in a later release.
• One name for the CEO's report: "Daily report", on the desk, in the e-mail digest option and subject, and in the Help.
• Wording: "Add a workstation" (with "Pair with a code" for pairing codes) everywhere; the BA designs the organization with the Owner and Admins; "Agents page" instead of "HR board".
• The in-app Help and page help were checked against the current app and updated section by section.
• Removed the unused CEO cooling-off setting (delayMinutes); saved policies that contain it still load.
• The retired .aom/test-env.json is no longer read.
• Self-hosting: a runner connecting to a server with a private certificate authority needs NODE_EXTRA_CA_CERTS (docs/SELF-HOSTING.md).

Fixed

• A bare skill key that is a playbook or a persona (release) is no longer rewritten to a pack skill of the same name when skills are qualified, and the key migration keeps it.
• Skills given to an agent (thanks to, ): the skills added to a role with Extend now reach every agent on the role, in chats, sessions and card shifts alike, as loadable skills in the # Capabilities index and the runtime's skills folder. Before, chats got only the skills stored on the agent at hire, and card shifts listed the extension's skills as plain text only.
• A bare pack skill name typed into the hire form or a role extension (bmad-prd) is stored as the pack's full key (bmad-method:bmad-prd) when exactly one pack has it, instead of showing as "not found in the registry". The data migration pack-skill-keys-2026-10 does the same for existing agents and extensions.
• Hiring with an empty Skills box gives the agent its role's skills (the form sent an empty list, which hired with none).
• An agent's skills follow its role: a new role version brings its new skills, and the agent's own additions and removals stay (AgentPermissionsRebased carries the skills).
• Reopening a published research card marks its publication superseded: the Research tab, phase completion and interest counts no longer count it, and publishing again leaves one live note.
• Reopening a bug card that was cancelled after a test failure puts its parent back to waiting when the parent is still queued or claimed in Test; otherwise both cards get a warning and the parent is left as it is.
• Media: a paused video is no longer cut after 30 seconds. Only real upstream silence (30 seconds) cuts a stream; a client that makes no progress for 10 minutes is closed. An upstream error mid-stream ends the response instead of throwing.
• Costs: the project filter lists every project, not only the selected one.
• Settings: you see and set your own time zone; non-Owners are told the daily report follows the Owner's zone.
• Intake and vault registration are offered only to people who may use them (desk, palette, empty board, discovery, Vaults).
• New research card from the Research tab starts on the research type.
• The org chart draws escalation to the CEO when one is active, as the routing does.
• CEO chat shows the error when the CEO status cannot be loaded, instead of "not set up yet".