Preview · npm beta 0.23.0-beta.1
Make every
collaboration compound.
A public preview of the next release, for people who want new features first. Below is everything it changes since stable 0.22.1.
$ npm install --global fuli-context@beta
$ fuli setup
Your Agents
Any folder,
any of your Agents.
Use @name or #FLA in any folder to have one of your Agents continue. Agent cards have “Copy #FLA” and a few ready phrasings to paste. Every new Agent gets a unique person-like name and a stable character portrait, with the job in its occupation and responsibility. Say once that a kind of work belongs to a project; after you confirm, matching tasks go to its lead.
@Milo Reed fix the login page forgetting “remember me”
Fixed: session.ts overwrote the remember flag during token refresh. Added two tests; both pass.
Across tools
Switch AI tools.
Keep your teammate.
An Agent’s role, working memory and conversations stay in FULI. OpenCode 2.x connects through a plugin to the task entry and close, with its own source (its conversations are not captured yet). WSL client paths are converted, so WSL clients reach FULI on Windows, and each client in the console has Update and Reconnect.
Sign-in refactor is halfway done: the API is ready; the frontend still needs connecting.
@Milo Reed continue yesterday’s login refactor
Picking up from the API. Next: frontend integration and regression tests.
Roundtable
The Roundtable,
like a chat.
Threads are a chat: your messages on the right, each Agent’s on the left. Message board waits for the Agent’s next working session; Live wakes it to answer now. Each message shows every recipient’s real state and, when a wake fails, why. @FLG brings in 2–4 Agents at once, each answering read-only in the Roundtable.
Milo ReedLive to Nova Lane
Have you reviewed the sign-in API changes? Anything I should fix?
Nova LaneWoken answers now
Reviewed. One change: clear the remember flag if token refresh fails. The rest is ready to merge.
Preferences
Tonborg,
with a reason every time.
The default judgment mode can be set per project. Every card waiting for you says why it needs you, and judgment records search all of their history. When a known injection pattern matches, the approval is held for you; it is a narrow extra check, not injection protection. Built-in Agents’ model keys are entered on the page, write-only, and every change is recorded.
Personal
TasteFewer gradients. No cards inside cards.
JudgmentDiscuss unclear direction before acting.
StyleBe direct and move work forward.
Project: shop-web
JudgmentDefault judgment mode: ask me first in this project
TasteShort sentences. No exclamation marks.
Project management
Every project,
its own manager and board.
Every space comes with three specialists: Jefa manages projects, Bole handles Agent resources, and Tonborg helps with judgment. A project can have its own project manager and board: custom columns mapped to the built-in states, or a link to an external board; Jefa’s board ships with FULI. A blocked task says what it waits for, since when and in which session, opens that session, and clears itself when the session continues. The Services page lists services Agents started; only you can stop them.
On demand
Titles first,
bodies when needed.
Change requests get a title index of matching knowledge, and the Agent reads bodies on demand. Starting a conversation takes one Provider request, and Claude Code’s task entry trims optional content to fit its preview limit while keeping hard rules and closing fields. In conversation memory, older messages fold into key points and recent ones stay verbatim.
Architecture
Before you upgrade,
know what changes.
Upgrading from 0.20.1, one graph migration needs your confirmation in Settings → Data format migrations, and the graph is read-only until then; a schema step and the Roundtable store upgrade run automatically after a backup. Older versions cannot open the upgraded data, so going back needs the backup from before the upgrade. Everything lives in the Neo4j graph on your computer, with history for every change.
Local-first
Your knowledge graph and conversations stay on your computer. Personal preferences stay out of shared layers.
You stay in control
You choose the autonomy level. Tonborg works within that authority and brings conflicts or decisions outside its scope back to you.
Context on demand
Retrieve only relevant, current knowledge for the task, rather than sending the entire history to the model. A task with nothing new to keep is closed by the Stop hook, saving a model round trip.
Everything that changed since stable 0.22.1
Everything this preview adds or changes compared with the current stable release, 0.22.1, not just what changed since the last beta. The release runs the full automated test suite before it is published, but it has not had the long real-world use a stable release has. Please report problems as GitHub issues.
New
- Health check: FULI checks for stale client connections, migrations waiting for you, sessions on an older version and unfinished updates. One click fixes what it can; for the rest it tells you where to go. The console shows “N things need you” at the top.
- The Windows package’s tray app is now the FULI desktop client: one sentence on whether FULI works, a card with one button per thing that needs you, a tray dot that changes colour and a notification when things get worse. It launches at login by default; turn that off in the tray menu.
- One-click update and rollback close the client first and open it again afterwards; uninstall closes it and removes its launch-at-login entry. A one-click update from the 0.22 tray opens the new client.
Changed
- The old FuliTray tray is no longer shipped and the Fuli shortcuts open the new client; Rollback-Fuli returns to the version you updated from, with its tray.
- Every console switch is the same component; the client takes its colours and type sizes from the console theme.
Before you upgrade
- No data format changes; upgrading from 0.22.1 needs no confirmed migration.
- The desktop client’s tray, notifications and launch at login are not yet verified on a real desktop; the macOS client is not in the release yet.
Install the preview with one command
If FULI is already installed, run fuli stop and back up the data folder first. These commands use the usual installers and only switch the package to fuli-context@beta; fuli setup runs afterwards.
curl -fsSL https://xn--8ovp9s.xn--m8txu.com/fuli/install.sh | FULI_NPM_PACKAGE_SPEC=fuli-context@beta shmacOS / Linux
$env:FULI_NPM_PACKAGE_SPEC='fuli-context@beta'; irm https://xn--8ovp9s.xn--m8txu.com/fuli/install.ps1 | iexWindows PowerShell
npm install --global fuli-context@beta && fuli setupnpm
To return to stable, run the installer again without FULI_NPM_PACKAGE_SPEC. The stable version is lower, so a native Provider needs fuli setup --allow-provider-downgrade. Data the preview upgraded, automatically or through a migration you confirmed, cannot be opened by an older version; only the backup from before the upgrade restores it.