tab_... IDs. Save those IDs when a later command
needs to address the same tab.
Open ordinary tabs
--project-path keeps filesystem paths out of internal page URLs. An anchor tab
controls placement only; it does not select the project. A project-aware chat
is born with the project’s metadata and in its canonical pinned project group;
it does not open as a scratch chat and move afterward. When splitting a new
project-aware chat, the anchor must already belong to that same project group.
--project-path applies only to a new radius://chat/; it cannot rebind an
existing radius://chat/?id=... conversation to another project.
Open a new tab in a split
Use an existing tab ID as the anchor:docs in the same tab row. Available directions are:
Control the split size
--size sets the new pane’s share as a fraction or percentage:
Split tabs that are already open
Open two tabs and then combine them:reference leaves its original group and joins page’s group. The resulting
split occupies page’s existing position in the tab order; it does not remain
at reference’s previous index. --right places reference in the right pane,
and reference receives focus by default. Add --keep-anchor-active to keep
page focused instead.
Remove a tab from a split
reference remains in the same group, keeps its position in the tab order, and
receives focus. In this example, it becomes an ordinary tab row immediately
after page. Because this is a two-pane split, page also returns to an
ordinary tab row.
Wait for a tab
Wait until a page finishes loading before the next command runs:COMMAND_TIMEOUT.
See Groups to organize ordinary tabs and complete split
layouts into named collections.