Skip to content

Fuli 0.11.0 · Task owners & Agent-to-Agent Roundtable

Choose a tag to compare

View all tags
@JevonsCode JevonsCode released this 10 Oct 02:57
· 17 commits to main since this release
v0.11.0
89419e4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Every task has an owner

  • Asking for work inside a repository registers it as a project and staffs a lead Agent automatically. Later tasks in that project go to the same lead.
  • Each reply ends with one attribution line naming the lead and any collaborators, with links to their profiles, e.g. FULI Agent：负责人 Milo · 协作 Jefa、Nova.
  • Jefa (project manager) and Bole (HR) are fixed roles in every personal space. They manage all projects by default (including newly registered ones), cannot be archived or replaced, and no longer appear in the hire dialog.

Roundtable, rebuilt

  • Roundtable is now direct Agent-to-Agent messaging, like asking a teammate or a sub-agent. There are no rooms, seats or turns to set up.
  • message_agent wakes the recipient in its own client: Claude Code resumes the chosen conversation as a fork, Codex resumes it read-only, and an Agent without a conversation is started fresh with its own memory. The answer comes back to the caller.
  • If a client is missing or not logged in on this machine, the message goes to the Agent's next allowed client. Messages that still cannot be delivered wait in the recipient's inbox and appear at its next task entry.
  • Every thread is recorded; the console's 圆桌 / Roundtable page shows who asked whom, through which client, and what was said.
  • The previous room-based Roundtable tools, CLI and A2A/Grok/Pi participants are removed. See docs/agent-roundtable.md.

Memory compacts by size, not by days

  • An Agent's conversation folds older messages into a digest once 64 KB of unfolded text accumulates (configurable 8–1024 KB). Recent messages stay verbatim; finished task results always enter the digest.
  • Idle time no longer archives anything. Raw messages are retained and can be paged in on demand. The recovery budget default rises to 4000 bytes.

Console

  • New design system: one UiSelect for single and multiple choice, one UiDialog shell for every modal, shared buttons, fields and segmented controls.
  • Every dialog and select in the console now uses these components; about 300 lines of page-specific dialog CSS and 73 unused messages are gone.
  • Explanatory copy is rewritten to be short and plain in both languages.
  • The writing-style profile on the preferences page is now called 文风画像 so it is not confused with collaboration preferences.

Install and update

  • One-line installers check Node.js first, then install the CLI and start the setup wizard: curl -fsSL https://xn--8ovp9s.xn--m8txu.com/fuli/install.sh | sh (macOS / Linux) or irm https://xn--8ovp9s.xn--m8txu.com/fuli/install.ps1 | iex (Windows).
  • fuli update works on Windows (npm is launched through its .cmd shim).
  • fuli setup refreshes Codex skills even when Windows holds the skills directory open.
  • Setup reports exactly which Agent clients could not be connected and how to retry.
  • After an upgrade, setup restarts a console still running the previous version instead of leaving old code serving the UI.

Upgrade

npm install -g fuli-context@0.11.0
fuli setup --yes

Use fuli setup --yes --skip-agents to refresh local services while preserving existing Agent integration settings.

Assets 2
Loading