You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Console/app: single-instance shortcut view with scoped notifications #784
PROBLEM — Today, getting to one specific agent instance means going through the general instance list every time, in both the console and the app. There is no way to save or pin a direct entry point to one instance, and notifications are not scoped per instance — you get everything or nothing.
ASK (client/console-facing, does NOT touch the MCP tool schema) —
A saveable, direct-entry view for a single instance — concretely, something that can be saved as a home-screen shortcut/bookmark (e.g. a stable URL per instance that opens straight into that instance's own page/chat, skipping the instance list).
Per-instance notification scoping — let a user opt into notifications for just one instance rather than all instances they own. Needs a settings surface (console and/or app) for choosing which instance(s) to be notified about.
NON-GOALS / CONSTRAINTS —
This does NOT replace or narrow the general multi-instance console/app view — the full instance list and cross-instance visibility must remain exactly as-is. This is an additive convenience layer, not a replacement.
Pure client/console feature. No MCP server, tool schema, or connector changes belong in this ticket — see the companion issue for the scoped single-instance MCP endpoint, which is a separate, platform-level piece of this same overall idea.
OPEN QUESTIONS FOR THE IMPLEMENTER — how a shortcut URL should authenticate (does it need its own token, or ride the existing session), what happens if the underlying instance is later deleted or renamed, and whether notification scoping is per-device or per-account setting. Please investigate existing patterns in the console/app before designing new plumbing.
RELATED — companion to the MCP-side ticket for a scoped single-instance connector (filed alongside this one); both originate from the same user request but are independent and can ship in either order.
Activity
feat(mcp): a session pinned to one instance at /mcp/i/<id>, publishin…
fix(console): satisfy the anonymous-type ratchet for #784 — reuse the…