Files
hyprland-headless-stream-pl…/docs/TODO
HermenixandClaude Opus 5 d788d5723e docs(mcp): what a shared transport does to the call-deadline limit
One property and one consequence, in the two places that own them.

`docs/CONTRACT-mcp.md` §1 gains the operational fact an operator meets
first: tool calls are serialised across every caller, not per session, so
two agents on two tokens queue behind each other.

`docs/TODO/mcp-in-process-has-no-call-deadline.md` gains why that matters
for the limit it already describes. The serialisation is not new -- it is
the same process-wide lock -- but over stdio a call only ever queued
behind the same client's previous call. One process for everyone means a
stuck call delays other people's agents, and whoever notices is not
necessarily whoever caused it. That makes the reachable-timeout idea
worth more than it was and the forked-child idea less unreasonable.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KchcvnbfhhZhUHy83YL3Ya
2026-10-11 22:44:53 +00:00
..

TODO

Known, unfixed problems — each one real, none of them guessed at.

Each file answers three questions and stops:

  • The issue — what is actually wrong, with the evidence for it.
  • Ideas — more than one, and which one is the recommended route.
  • Why it matters — the impact, not the principle.
item severity state
cursor-visibility-in-captures high answered: the compositor draws no cursor for a virtual pointer. Needs a decision on an overlay marker
scroll-has-no-compositor-proof medium works live; unproven in a gate
reconcile-while-containers-are-off medium partly fixed: discovery now survives a restart; teardown still lives inside the feature
kill-can-leave-the-app-alive medium found by counting windows, not sessions
capture-binary-and-the-unit-path medium found the first time the app was run as a unit: a unit's PATH has no grim
mcp-in-process-has-no-call-deadline medium two costs of running the CLI in process: no killable deadline, and no sg recovery
mcp-resources-cannot-be-subscribed-to medium the SDK hardcodes subscribe=False, so a log resource can only be re-read
mcp-http-auth-is-not-oauth medium a static bearer token, not OAuth 2.1 + RFC 9728: the cost is which clients can connect, not how exposed the desktop is
mcp-tokens-do-not-scope-resources medium token mint --toolsets frames narrows the tools and not the eight resources; nothing until a second token is minted for someone else

Closed since this folder was written:

  • "Containers do not bind" — fixed. Windows are assigned by the pid the compositor reports, moved onto their desk's workspace and read back. Two sessions now hold two outputs with a real browser on each.
  • "The pointer is unusable while containers are off" — fixed with it. The pointer aims at the session's desk, and desks hold applications.
  • "Discovery refuses when two compositor instances exist" — fixed. Each candidate is asked for its version and the one that answers is used.

Severity here means "how much of the feature is actually delivered", not "how loud the failure is". The highest is highest because a whole class of work is blocked on it: the pointer is exact and invisible, so nothing can show where anything happened.

When one of these is fixed, delete its file and the row — this folder is a list of what is still true, not a history of what was thought.