Thanks: your idea is implemented and ships in the next release. We built it the way we pictured it, so if the result is not what you had in mind, tell us and we will adjust it.
Editor opens only files inside the open project's tree; no Ctrl/Cmd+O or file picker to open an arbitrary file elsewhere on disk
From Pedro FigueiraDone 1 month ago
An AgentsRoom project is scoped to one directory tree and the file navigator only exposes files under that root. When a file lives OUTSIDE the tree — a log in /var/log, a dotfile like ~/.zshrc or ~/.ssh/config, a snippet in an unrelated folder — there is no fast way to open it. The only workarounds are heavyweight: leave the app for an external editor, or add the file's folder as a whole new project just to read one file, which clutters the project list.
Full report: https://claude.ai/artifact/3NyKg2UixEEpKbjyeq3yTr
How this was scoped: from using the app (read-only observation of product behavior), NOT from reading the AgentsRoom source. Claims split into Observed vs Inferred in the report.
Proposal (in decreasing order of value):
- PRIMARY — an "Open File…" command bound to Ctrl+O / Cmd+O and mirrored in a menu item, opening the OS file picker; the chosen file opens in the editor even when it is outside the project tree.
- Quick open by path — an input accepting an absolute or ~-relative path.
- Optional — a short "recently opened external files" list, kept separate from the project's own history.
Not asking for: indexing/watching the external folder, adding the file to the project tree or search scope, or a full multi-root workspace — just "open one arbitrary file".
The one real design decision is how an out-of-tree file is presented (a distinctly-marked tab, whether edits are allowed, where it appears). A rough sketch is in the report.
AgentsRoom diagnostics
- App version: 1.171.0
- OS: linux 7.0.0-31-generic (x64)
- Agent CLI: claude
- MCP server: 1.22.0
- App language: system
Problem to solve
Projects are scoped to one directory tree and the file navigator only lists files under that root. There is no shortcut, menu item, or picker to open a file that lives outside the tree — a log in /var/log, a dotfile in the home directory, a snippet in another folder. Peeking at or editing such a file forces the user out of AgentsRoom or forces adding its folder as a whole separate project. Low cost per occurrence, but constant, and it pushes routine file work out of the app.
Proposed behavior
Add an "Open File…" command bound to Ctrl+O / Cmd+O and mirrored as a menu item. It opens the OS file picker and loads the chosen file in the editor EVEN WHEN it is outside the open project's tree. Complementary, in decreasing value: (1) quick open by path — an input accepting an absolute or ~-relative path; (2) the menu entry for discoverability; (3) optional "recently opened external files" list, kept separate from the project's own file history. Out-of-tree files should be visibly marked as not belonging to the project.
Who benefits
Developers who use AgentsRoom as their working environment and regularly need a file that is not part of the current project: reading a service log under /var/log next to the code that produced it, editing a dotfile such as ~/.zshrc or an SSH config, or pulling a reference snippet from an unrelated folder — all without leaving the app or importing that folder as a project.
Acceptance criteria
From anywhere in AgentsRoom, press Ctrl+O / Cmd+O (or use the menu), pick any file on disk, and it opens in the editor in a tab clearly marked as external to the project — no need to switch to another editor or to register the file's folder as a new project. Routine "open one arbitrary file" tasks stay inside the app.