AI Observer / Runtime-Aware Dev Agent

Follow-up idea: AI Desktop Shell 0.1 / Runtime Beacon A natural extension of AI Observer would be the ability to attach the assistant to the actual place where the user is working, almost like dropping a location beacon on a map. Instead of only chatting with an AI, the user could pin the AI to a specific browser tab, extension popup, app window, terminal, file, dev server, DOM element, or screen region. The user could point at the problem and say: work here. The assistant would immediately know the active runtime context. For Windows, this could start as a lightweight desktop overlay rather than a full OS replacement. It would sit above the normal desktop and provide Pin current window, Point to region, Observe, Safe test, and Continue. Under the hood it could combine screenshot and OCR, accessibility tree, process and window metadata, browser DOM and console when available, and terminal or dev-server logs. The key UX is that the AI should always know and show what it is attached to: active app, browser tab, popup, worker, process, or selected screen region. It should report status such as attached, observing, testing, blocked, needs confirmation, runtime error, or ready. This would let a developer literally point the assistant at an app and say: fixed it, test again. The AI would not need repeated explanations; it would already have the beacon, the runtime surface, and the project context.