Overview
Terminal and tmux collections can switch between grid and list views so the amount of visible metadata matches the number of active sessions. Each item exposes its Host, Project, or Action context to make the current work site easier to identify.
Long-press and swipe actions provide direct management operations such as rename and delete. Clear session names and deliberate cleanup make it much faster to return to long-lived work later.
When to use it
- Scan active work across several Hosts, Projects, agent sessions, shells, and background tmux tasks.
- Use grid view for visual recognition when there are fewer sessions and list view for denser scanning when there are many.
- Rename a long-lived session after its purpose changes so it remains understandable days later.
- Swipe or long-press to remove disposable terminals and stale tmux entries without opening each one first.
- Separate implementation, test, preview, log, and production-diagnostic sessions with consistent names and visible context.
Scan many active work sites
Use list view to compare Host, Project, Action, session name, and activity state when several agents, shells, logs, and background tasks are open at once.
Preserve important sessions with clear names
Rename a long-lived terminal or tmux entry from a generic command name to its actual purpose, such as checkout fix, release verification, or production logs.
Clean up without opening every item
Use long-press or swipe actions to remove disposable terminals and stale sessions directly from the collection, keeping the remaining workspace easier to scan.
How it works
- Choose the grid or list layout that matches the number of sessions.
- Identify sessions by Host, Project, and activity state.
- Use long-press or swipe actions to manage a session without opening it first.
Practical guidance
Use consistent Host, Project, and tmux session names. Clear naming makes the workspace controls much more useful when several agents are running at once.