Skip to content

Read the agents snapshot of newer cores - #58

Merged
ChrisPlayer merged 1 commit into
mainfrom
fix/settings-open
Oct 25, 2026
Merged

ChrisPlayer merged 1 commit into
mainfrom
fix/settings-open

Conversation

@ChrisPlayer

Copy link
Copy Markdown
Contributor

Bots works again with a Boite whose agents are threads.

Why

Since Boite made each bot a thread (Boite #747), agents.snapshot sends no messages, work or deliveries, and its sessions have no scope. Bots read them as before and threw on every update (reading 'filter' on work, reading 'kind' on a session's scope). The page stopped answering: a click on the island, its hover and Settings from the tray did nothing.

What changes

  • Every agents.snapshot read, this machine's and the other machines', goes through readableSnapshot (lib/group/agents.ts): a list left out reads as empty, a session without a scope as the agent's direct one.

Checks

  • bun run check: 0 errors, 0 warnings.
  • vitest: 77 files, 552 tests. New: a newer core's snapshot reads without breaking the island.
  • The two errors were read from the v0.1.20 page's console, run against a current Boite.
  • The fixed build was not run against it.

Not in this PR

The deck's chat still reads the old conversation records, which newer cores no longer send: it shows no history there. Porting it to agent threads is a follow-up.

Since bots became threads in Boite, agents.snapshot sends no messages, work or deliveries, and its sessions have no scope. The island read them as before and threw on every update, so the page stopped answering: no deck, no Settings.
@ChrisPlayer
ChrisPlayer merged commit 5ca378a into main Oct 25, 2026
3 checks passed
@ChrisPlayer
ChrisPlayer deleted the fix/settings-open branch October 25, 2026 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant