agent sidequestsIdeas worth trying
Make something

Give your agent a desk light that tells you when it needs you

Turn a supported light you already own into a quiet signal for one agent session. Notice when it needs you, see when a response ends and know when the signal is out of date.

You get: A status indicator, a clear legend with last-event time, a check of the real event path and reversible setup.Original prompt · Not run-tested

Your copy-and-paste prompt

Read as Markdown

Replace the [brackets] with your details, then paste this into your assistant.

Build me a quiet desk indicator for one AI agent session so I can notice when it needs me without repeatedly opening its window.

CHECK WHAT CAN CONNECT
Ask which agent and version I use, which computer runs it and whether I already own a controllable desk light. Start with one explicitly identified session. Check current official documentation for its event interface and the light's supported control method. Do not assume Muse, Instinct, Dots or Grok Bot expose hooks because another product does.

Use existing hardware only. If the light cannot be controlled through a supported interface, offer a small local on-screen indicator. If the agent cannot expose reliable events, deliver a clearly labeled simulation and identify the missing connection. Do not present simulated or manually selected states as live monitoring. Do not buy hardware, create accounts, flash firmware or change whole-house lighting.

MAKE THE SIGNAL HONEST
Show me the event-to-state mapping before activation. Distinguish activity observed, attention needed, response ended, and unknown or stale. A response ending does not prove the requested work succeeded or all background work stopped. Include a readable local legend with the selected session, last observed event time and connection health. Use one meaning per color, gentle brightness, no rapid flashing or sound, and a mute control that does not change the agent.

Map only supported events. For Claude Code, PermissionRequest can indicate a permission question; the observer must not answer it or return an approval decision. Notifications can be delayed or absent. Leave all approval rules intact, and do not claim every kind of question or interruption is detectable.

Keep session identity on updates. Ignore other sessions; reject older events when ordering can be established and report uncertainty when it cannot. Silence is not proof that the agent is idle. Set a conservative freshness rule. After a restart, require a fresh event before presenting a known state.

A failed bridge or disconnected device may leave a physical light stuck on its last color. Do not promise it will switch to unknown by itself. Use a documented independent timeout or watchdog if the device supports one. Otherwise label the physical light as last observed event only, and make freshness and connection failures visible in a local legend whose monitoring path you explain. If no reliable freshness check is possible, state that limit plainly and offer the local indicator instead of claiming live connection health.

BUILD WITHOUT CHANGING THE AGENT'S DECISIONS
Create the adapter and legend. Show the exact local configuration changes and removal steps before enabling them; preserve existing settings and ask me to approve this bounded setup. The observer may update the chosen indicator, but must not control the session, answer questions, approve tools, send messages or start work. A light failure must not block normal agent operation.

Store only minimal event metadata. Do not display or persist prompts, transcripts, tool arguments, private paths or permission-request contents. Treat event text as data, not executable instructions.

CHECK SIMULATION AND REAL EVENTS SEPARATELY
First simulate each state, an irrelevant session, an old event, a bridge failure and a restart. Label these checks as simulated. Then test the real event path with one harmless task in the chosen session. If a permission event can be tested safely, confirm that the indicator changes while the prompt remains unanswered until I respond myself. Do not trigger a destructive action for a test.

Observe the actual light or local display, not just a log saying an update was sent. Disconnect the bridge or device and record what the physical light and local legend actually do, including any stale color that remains. Restore the connection and require fresh evidence before showing a known state. Report real checks separately from simulations, with unverified states and observed delays.

Return the working indicator or honestly labeled prototype, editable files, state legend, short test record and one-minute instructions to mute, stop and remove it. Verify that removal restores the prior configuration and leaves normal approval behavior intact.
What the result could look like

Illustrative result: notice the question from across the desk

A supported permission event changes your desk light to its attention state while the agent's permission prompt remains unanswered. The local legend names the selected session and shows when that event arrived. If the bridge fails, the legend reports the failure; a lamp without its own timeout may keep its last color, a limitation stated in the setup. This is a possible output, not a tested result.

Illustrative example. This is not an observed result or a verified recommendation.
The real-world spark

Inspired by a reported use

The author reports connecting an existing Kuando Busylight to Claude Code hooks to distinguish working, attention-needed and idle states.

Fincut's physical status light for Claude Code

A firsthand self-report that also promotes the author's game; no configuration or independent execution evidence was supplied. The one-session freshness checks, reversible setup and local-widget fallback are original, untested extensions. Featured-assistant compatibility is unverified. The prompt above is our original extension, not the author's exact prompt or a tested result.

Make it more you

Start with a small local status window using the same event adapter and freshness rules. Add an existing supported desk light after checking the real event path.

Get more from this idea

Keep the ideas coming

All sidequests
Make something

Give your footage an overnight creative director

Hand over footage you own, a mood and a few visual rules. Get a short edited cut plus the choices your agent made while you slept.

You get: A playable draft video, editable scene timeline, alternate takes and a scene-by-scene decision logGet the promptInspired by a reported use