Terminals
Side panel & files
The side panel beside the board and every open card or shell, its Files and Shells tabs, and opening files in your editor.
On this page
The side panel sits at the right of the window, beside a workspace's board and beside every card or shell you open. It has two tabs: Files, a file explorer of the folder you are working in that marks what git sees as changed, and Shells, the workspace's shells and triggers. This page covers both and how files open in your editor.
Show, hide and resize it
The panel shows by default. To show or hide it:
- click the panel button at the right end of the title bar (Show panel / Hide panel);
- press ⌥⌘B / Ctrl+Alt+B (default shortcut), also while a terminal has focus;
- pick Toggle panel in the command palette.
It is one panel for the whole app: hiding it beside one card hides it beside the board and every other card too, and it stays hidden after a restart.
Drag its left edge to resize it, from 200 px up to half the window. You can also focus the edge and use the Left and Right arrow keys (16 px a press). Bikube keeps the width, and the tab you last picked, across restarts.
In the main window, the panel's tabs and its button sit in the title bar above it. A card window, which has no title bar, shows them in the panel's own header.
The Files tab
The Files tab shows the folder of what you are looking at:
- beside a card, the card's own folder (a worktree card's worktree);
- beside a shell or the board, the workspace's folder.
The top row is the folder's name (hover it for the full path). Below it, folders come first, then files, each sorted by name, numbers in natural order (file2 before file10). Hidden files are listed; .git isn't. A folder's contents are read when you expand it, and Bikube remembers which folders you expanded until it quits. A folder with more than 2,000 entries lists the first 2,000 and a last row such as … 312 more.
- Symbolic links show an arrow. One that points to a folder inside the shown folder expands like a folder.
- The tree works from the keyboard: Up and Down move, Right and Left expand and collapse, Enter opens a file.
Git changes
In a git repository, the tree shows what git sees:
| Mark | Meaning |
|---|---|
| M | Modified |
| A | Added (a new file, staged) |
| D | Deleted: the file still shows, struck through |
| U | Untracked |
| R | Renamed (its tooltip names the old path) |
| C | Conflicted |
| Dot on a folder | Something inside it changed |
| Dimmed entry | Ignored by git (.gitignore, .git/info/exclude or your global excludes) |
Changed only, in the tab's header, narrows the tree to the changed files and the folders that hold them, all expanded; with nothing changed it reads No changes. Outside a git repository it is disabled (Not a git repository).
While the tab shows and Bikube's window is focused, the tree and its git marks are read again every 3 seconds, and at once when the window gets the focus; Refresh reads them now. Bikube only reads: it never changes a file, and its git reads never take the lock an agent's own git needs.
Open a file in your editor
Double-click a file, or select it and press Enter, to open it with the Editor setting (Settings, Editor, Open files with):
| Choice | What opens |
|---|---|
| VS Code (default), Cursor, Zed | The shown folder as the project, with the file in it, reusing that folder's window when it is already open. |
| System default | The app your system opens that kind of file with. |
| Custom command | Your one-line command, run by your shell with the file's path added at the end; for example subl -n runs subl -n '/path/to/file'. |
Editors run through your login shell, so they are found on the same PATH as in your cards. An editor Bikube can't find on this computer shows (not installed) in Settings. When an editor can't start, the tab shows why, such as Couldn't open app.ts: code not found, until the next open.
SSH workspaces
For a card or shell of an SSH workspace, the Files tab reads Files aren't available over SSH yet.
The Shells tab
The Shells tab lists the workspace's Default shell, its named shells and its triggers, with how many are running on the tab itself. From it you start, open, stop, edit and move shells, and see their dev server chips. See Shells & triggers.
Checked against Bikube 0.9.1