Files

T

pastilhasandClaude Opus 5 6b07aafc67 spotlight opens on alt-space, and on nothing else

Third chord in a day, and each move was the owner naming a collision on the machine he actually uses:
ctrl-space is Brave's address bar, shift-space types a space, alt-space is the window menu — and he rebound
that rather than give up the chord.

Shift-space was the worst of the three and it is worth saying why, because it read as the safe choice.
It is a real key combination inside a text field: it types a space, and people hold shift through one more
often than they think while typing capitals. So it had to stand down whenever focus was in an input — which
is where focus usually is, the chat composer — and a launcher you have to click out of a field to reach is
not a launcher.

Alt-space means nothing in a text field, so the isTyping guard stops being the thing holding the feature up
and becomes belt-and-braces. Kept anyway: two lines against some layout delivering alt-space as a literal
character, which is cheap to prevent and expensive to discover.

`altKey` with `ev.code`, not `ev.key` — alt-space produces a different `key` on several layouts and nothing
at all on others, while the physical key is `Space` everywhere.

No second chord. Two triggers for one thing means two things to collide with, and this one has moved twice.

The TODO item's id still says ctrl-space. Ids are stable by design, so it stays; its body now records all
three moves and which guard was load-bearing for which.

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

2026-08-22 03:31:44 +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

85 open, 22 closed, across 28 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	18	3
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
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-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
2026-08-21 Settings to choose which server each feature uses — fleet/settings-to-choose-which-server-each-feature
2026-08-21 'A deploy verifies PM2, not that the app still works' — fleet/a-deploy-report-verifies-pm2-not-that-the-app