Repository navigation
cell 0.1.6 — the shell rebuilds itself around semantic events
Highlights
- The desktop shell is rebuilt around a three-column frame. Sessions on the left, the conversation in the middle, and a right-hand panel with 文件 / 改动 / 日志 — open a file in a highlighted viewer (capped, binary files announced rather than rendered), see what this session wrote or edited, and tail the runtime log. The trace view carries the approval audit and full sub-agent control.
- The live turn is rendered from the kernel's own semantic events.
token,reasoning,tool_call,tool_result,usageandinterruptare emitted through a process-wide sink that only the service layer installs, so the CLI still pays one null check per delta. Tool events are paired by id, andusage.decode_msstarts at the first token, so tok/s is measured rather than flattered. - Drive the sub-agents from the shell. A launcher where each line is one child's task (parallel or serial, the kernel names the children), run / stop / resume / staff a pending job, and read each child's report — with controls that appear only when the job's state allows them.
- New REST surface, all gated:
GET /v1/files+/v1/files/content,GET /v1/logs?tail=, thenoticeevent and?follow=1, per-worker teamwork reports,POST /v1/sessions/{id}/clear|archive|unarchive,GET /v1/sessions?archived=1,POST /v1/uploads+GET /v1/uploads, the approval audit, and exports asjson|md|html— the last one being the same self-contained page the CLI writes, so a browser gets the full export too. - Providers are manageable from the shell now (list, add, probe the model list, rotate a key, switch, delete), and the settings panel says where your data lives and whether that place can be written.
Fixes
failed to fetch, for real. The server closed sockets with unread data still in the receive queue, which makes the kernel send RST instead of FIN — and an RST discards the response the client has not read yet. A browser reports that as a failed fetch. The socket is now drained (50 ms, bounded) before closing, and the three paths that used to close a connection without logging a word (the worker'scatch (...), a failedrecv, a failedsend) now say why.- cellui no longer re-asks for your endpoint on every launch. The runtime root defaults to a directory beside the executable — read-only when cellui lives under Program Files — and the config write failed silently, answering 201 for a provider that only ever existed in memory. cellui now probes the root at startup and falls back to a per-user location, config routes answer
500 config_unwritablewith the path, and/v1/healthreportsroot+root_writable. - MSVC builds again.
std::chrono::file_clock::to_sys()does not exist on MSVC (itsfile_time_typeis measured on the filesystem's own clock), which broke everymtimethe REST layer reports.unix_seconds()now calibrates against that clock'snow(), andtests/msvc_check.shcompiles the helper straight out of cell.cpp withcl.exe— no vcpkg, no vcvars. - Failures in the shell speak the user's language: a sentence with a next step instead of
TypeError: Failed to fetch, quiet retries for the background pollers, and a turn whose stream dropped asks the kernel whether it ran before reporting anything.classifyErrornow prefers the kernel's precise code over the coarse HTTP status. - Sessions can be deleted (armed twice, because deleting takes the transcript with it), and a second turn now waits its turn instead of returning 409, reporting
waited_ms.
Docs
docs/RESTful.md is the contract for every route above, with the roadmap rewritten as Done (P1) plus three later items and the reasons they are later. docs/DESKTOP_UI.md records the redesign P1–P11. README.md and README_zh.md stay in sync.
Packages
| File | |
|---|---|
cell-v0.1.6-windows-x64-msvc.zip |
cell.exe + cellui.exe (static, no runtime DLLs), README, LICENSE, brand |
cell-v0.1.6-linux-x64-gcc14.tar.gz |
same layout, static |
cell-v0.1.6-macos-arm64-appleclang.tar.gz |
same layout, static |