Files

T

pastilhasandClaude Opus 5 c982353381 the boot check now reads the sockets that are served, not a list beside them

assertPermissionTotality exists to refuse a surface nobody has gated, and it was reading the wrong list:
Object.keys(handlers) — the map of implementations — while Bun served a hand-written route table twenty
lines away. The comment beside it said neither could be a stale copy of the other. That was false, and it
had a live instance: /api/cliamp/ws and /api/cliamp/audio/ws stayed in the route table for two days after
their handlers and registry claims were commented out. Not exploitable — isWsProviderAllowed finds no
permission and 403s a member, while the owner upgrades onto a dead socket — but precisely the drift the
guard is for, invisible to the guard.

Now there is one declaration. WS_ROUTES maps path → provider, the route table is generated from it, and the
check reads it. A socket route cannot exist without being checked.

Two smaller guards arrived with it. A route naming a provider with no handler refuses to boot, with the path
in the message, instead of 500-ing on first connect. And the provider union that was inline in upgradeWs is
named, so the route table typechecks against what that function can actually serve — which caught my first
attempt, where WS_ROUTES was Record<string, string>.

sidecar and dev-proxy are listed explicitly as served-but-absent-from-WS_ROUTES, because they upgrade
through their own handlers rather than upgradeWs. Named so the absence cannot read as an oversight.

Half the TODO was stale and it is recorded as such rather than quietly closed: the eight red tests it cites
have been green since cliamp was deleted on 2026-08-15. Deleting cliamp removed the symptom and left the
shape, which is the more interesting half.

Verified against the real prefix lists rather than by reasoning: the served set passes, one unclaimed
provider is refused by name, all five generated routes answer 401, and the server boots.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-22 04:25:48 +00:00

5.4 KiB

Raw Blame History

TODO — the index

Deferred work. The items live in todo/, one file each, grouped by theme; this file is the map over them and is GENERATED — run bun run todo:index after any change rather than editing it here. Format and the two-way-sync contract: todo/README.md.

Context, corrected 2026-08-07. This list used to open by saying Officer was "collapsing from multi-tenant / open-source-ready to a single-user platform", and told you to treat multi-tenant indirection as accidental complexity. That direction was reversed. The permission model shipped on 2026-08-07 to serve a real goal — deploy to the company server, onboard people, give each one their own Gitea account through the platform. Per-user scoping is now a requirement, and the items that proposed deleting it have been removed rather than left to mislead the next reader.

What did NOT reverse: execution permissions (terminal, chat, tasks, files, desktop, browser) run as the owner's OS user and can never be granted. Indirection there really is accidental complexity.

Urgent

due 2026-08-22 — Settings to choose which server each feature uses — fleet/settings-to-choose-which-server-each-feature

Themes

86 open, 23 closed, across 29 themes.

Theme	Open	Closed
Affordances	1	0
Speaking into a session from the backend	2	0
Backburner	2	0
Background jobs	2	0
Chat interface	1	0
Code editor	1	0
Components — the shared UI layer	1	0
File watchers	1	0
Fleet — one command across every server	5	2
Headscale	0	5
Infra (alpha)	6	0
Known bugs	4	1
Mobile apps	3	0
Multi-user	17	4
Notifications	1	0
Plugin ecosystem — before it opens to third parties (2026-08-18)	3	0
Plugin infrastructure	2	0
Plugin repos — what writing their READMEs turned up	10	9
Plugin system — gaps the email extraction found (2026-08-18)	3	0
Prompt library	1	0
Settings — portable, and readable by an agent	2	0
Shell — spotlight and the dock	1	1
Sub-agents — agents spawning agents	1	1
Sudo terminal modal	1	0
Tooling — the list about the list	1	0
Transmission	6	0
URL state — routing, query strings and selection	4	0
Waiting on the owner to run it	2	0
Workspaces & Panels	2	0

Records — no items, kept for the reasoning

Newest ten

2026-08-22 A plugin's permission should be on for every role by default, off only on request — multi-user/a-plugin-s-permission-should-be-on-for-every
2026-08-22 A user's settings should export and import as a plain file — settings/a-user-s-settings-should-export-and-import-as
2026-08-22 The same for system settings, owned by the Super Admin — settings/the-same-for-system-settings-owned-by-the
2026-08-21 No way to see which affordances are reaching your agents, or to turn one off — affordances/no-way-to-see-which-affordances-are-reaching
2026-08-21 Generalise it: deliver a turn to a named session, from anywhere in the backend — agent-delivery/generalise-it-deliver-a-turn-to-a-named
2026-08-21 The cost of resuming grows with the transcript — agent-delivery/the-cost-of-resuming-grows-with-the-transcript
2026-08-21 'An agent spawned by a background job is invisible in the interface' — background-jobs/a-spawned-agent-is-invisible-in-the-interface
2026-08-21 Show how long a turn took, beside its cost and tokens — chat/show-how-long-a-turn-took-beside-its-cost
2026-08-21 Map every custom component, centralise it, and let a theme override it — components/map-every-custom-component-and-centralise-it
2026-08-21 Watch a directory, and attach actions to what lands in it — file-watchers/watch-a-directory-and-attach-actions-to-what