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
What problem does this solve? (describe the problem you're experiencing)
Currently, pressing @ in Chat (Assistant mode) only allows attaching tabs. But when working on a task, I often need to reference files from the workspace, past memories/conversations, bookmarks, or scheduled task outputs — not just open tabs.
The @ shortcut feels underutilized — it could be a powerful context picker like IDE-style @ menus (VS Code, Cursor, etc.) that can attach any type of context.
How are you working around this today? (your current solution or workaround)
Manually copy-pasting file contents into the chat
Leaving tabs open just to attach them via @
Using memory search as a separate step before asking questions
No good way to attach bookmarks or scheduled task outputs as context
What's your proposed solution? (how should BrowserOS address this?)
Extend the @ picker to support multiple context types beyond tabs:
Additional context (optional - add screenshots, examples, or other helpful details)
This mirrors the IDE pattern (VS Code/Cursor @ menus) — low learning curve for dev users
A single @ press could show all available types, then filter as you type: e.g. typing "do" could match files like "docker-compose.yml", memories about "docker setup", and tabs with "docker" in the title
What problem does this solve? (describe the problem you're experiencing)
@in Chat (Assistant mode) only allows attaching tabs. But when working on a task, I often need to reference files from the workspace, past memories/conversations, bookmarks, or scheduled task outputs — not just open tabs.@shortcut feels underutilized — it could be a powerful context picker like IDE-style@menus (VS Code, Cursor, etc.) that can attach any type of context.How are you working around this today? (your current solution or workaround)
@What's your proposed solution? (how should BrowserOS address this?)
@picker to support multiple context types beyond tabs:Additional context (optional - add screenshots, examples, or other helpful details)
@menus) — low learning curve for dev users@press could show all available types, then filter as you type: e.g. typing "do" could match files like "docker-compose.yml", memories about "docker setup", and tabs with "docker" in the titleThanks for sharing your idea! We love hearing how we can make BrowserOS better. ✨