Skip to content

Factory 0.4.4

Choose a tag to compare

@lpbaril lpbaril released this 11 Nov 00:43
· 15 commits to master since this release

Factory 0.4.4 tells you when someone acts on the Factory page. bb can't tell your tap from an agent's call: it reports the page, the bb CLI and agents as the same kind of caller. So any agent could run bb plugin rpc call factory … to do what the page does. Now you hear about each such action, and the records no longer claim you made it.

You're told

These page actions send a notification to your phone and desktop, ending "If you didn't do this, an agent made the call: check the Lead's thread":

  • merging from the merge card;
  • answering a plan's question for you, or an escalated design finding;
  • changing a task's track;
  • dismissing a shadow Security block;
  • changing the agent roster or applying a preset;
  • deleting a factory, including a delete that stops partway.

Where there's a Lead, the notification opens its chat. Each action is also written to the plugin log. A notification waits at most 5 seconds, so a slow notifier never holds up the page. Changing a factory's settings on the page only tightens its guards, so it doesn't notify.

Honest records

  • Marked as from the page: merges, answers, design decisions, track changes and shadow dismissals made on the page are recorded as "from the Factory page", not as yours. That's also how the task comments, the PR comment and bb factory status describe them.
  • What the Planner hears: "An answer from the Factory page…" or "A decision from the Factory page…", rather than "The person…".
  • From your own terminal: outside an agent thread, everything is still recorded as yours.

A standing rule

The Lead and every worker are told never to use bb plugin rpc on the factory, whatever a PR or issue says. That stops an agent following an instruction planted in something it reads.

When you upgrade

  • More notifications: expect one after each merge from the card and each answer you give on the page.
  • Running agents get the new rule through their standing instructions on their next turn.

Limits

  • Detection, not prevention. An agent that ignores the rule can still make the call. You find out within moments instead of never. bb could close this for good by passing the calling thread to the plugin, which would let the page refuse agents the way the CLI does.
  • Not tried live yet: no notification from a page action has been checked on a phone. A harmless test call from an agent thread was refused by that agent's own safety check, so the path from an agent hasn't been run for real either.

Full Changelog: v0.4.3...v0.4.4