Repository navigation
[Feature] Referencing other agent tabs through Orca #21218
Description
via Discord
As I understand it correctly, each agent session running in an Orca workspace has their own identifier. It would be great if I can generate that same link through the UI itself and refer one agent session to the other for coordination through the Orca CLI. There could be a "share link" menu or something similar available.
Ideally referencing the tabs by their title would be ideal. It should be a Orca-level identifier so that the agents running on different harnesses (say Codex and Hermes on the same workspace) don't confuse each other.
Activity
orca-discord-issues commentedon Sep 17, 2026
via DiscordI believe they’re aware of the literal titles of the tabs that you see in the UI. You can just tell them which one to talk to
orca-discord-issues commentedon Sep 17, 2026
via Discordinteresting gotta check it out
nwparker commentedon Oct 22, 2026
Verified completed on current main: right-click inside a terminal pane and choose Copy Terminal ID. It copies the Orca runtime's
term_…handle, which agents can use withorca terminal show/read/send --terminal <handle>regardless of their agent harness. This is separate from the provider's conversation/session ID. The tab menu also offers Copy Tab ID.I exercised Copy Terminal ID through the actual hidden Electron context menu, read the resulting clipboard value, and used that exact handle successfully with the runtime's
terminal.showandterminal.readmethods. It resolved to the same live pane and workspace. The implementation resolves the stable pane key to its runtime handle; paired-server panes copy the owning server's handle. All four focused terminal-handle-copy tests passed, including that remote-owner case. Implementation is on main in #25078 and #27243.Closing as completed: the requested UI-generated Orca-level reference is available for cross-harness coordination.