Mirasim Documentation
Files, Git and terminals
The code side of the workbench: browse and edit the real repo, jump through it, review and commit, search everything, preview what came out.
The file tree, and file operations
The explorer shows the real workspace with Git state on every row: how many files changed inside a folder, which files are modified or untracked, what Git is ignoring. When an agent writes a file, the row updates — you are watching the repository, not a cached listing.
The treeThe real workspace with Git state on every row — what changed, what is untracked, what Git is ignoring. — this control is not on the captured screen.
The buttons in this panel work — click them to look around.
It is a working file manager, not a read-only view. From a row's context menu: open, open to the side, open with another app, reveal in Finder, copy the file, copy its path or relative path, cut, paste, rename, duplicate, move to trash, and create new files and folders.
FilesThe explorer for this pane's workspace, with Git state on every row. ⇧⌘E gets you here from the keyboard. — this control is not on the captured screen.
The buttons in this panel work — click them to look around.
Editing and navigating code
Files open in a full code editor with syntax highlighting, and Markdown, JSON and other structured formats get a view mode, a source mode, a split of the two, and a preview. JSON gets real parse errors with line and column, and tolerates comments and trailing commas while warning that strict parsers will not.
Code intelligence works the way you expect it to: ⌘-click a symbol to jump to its definition, and look up every other place it is used. When there is nothing to find, it says so instead of jumping somewhere plausible.
- ⌘clickGo to definition
- ⌘FFind in the current file or transcript
- ⇧⌘EFocus the explorer
Reviewing and committing
Source control is a full panel, not a status line: staged changes and unstaged changes, a diff for every file, and the operations you would otherwise switch to a terminal for. Diffs render side-by-side or inline, original against current.
- Stage / unstage
- Per file or everything at once. Discard a file's changes, or delete an untracked file — both confirm first, because neither can be undone.
- Commit
- Commit staged changes, commit everything, or commit and push in one action, with the message written in the panel.
- Branches
- See the current branch, switch branches, and see how far ahead or behind the upstream you are — or that there is no upstream yet.
- Pull / push
- Both, with the failure cases named rather than dumped as raw Git output.
- Restore
- Roll a single file back to HEAD, staged and unstaged changes together, after an explicit confirmation.
When an operation does not go through, the panel says which of the ordinary Git situations you are in — local changes would be overwritten, the branches have diverged, no upstream, the remote has commits you do not, an unfinished merge or rebase, refused credentials, an unreachable remote, a hook that rejected it — and offers the move that resolves it, such as stash-and-pull or pull-with-rebase. Nothing has moved when you see one of these; the message tells you what will happen if you take the offered action.
Searching files and searching conversations
Two different searches, because you are looking for two different things.
In the code
Filter the tree by filename, or search file contents across the workspace with match case, whole word, and regular expressions, narrowed by include and exclude globs. Results are grouped by file with a count of matches and files, and the search tells you when it truncated rather than pretending it found everything.
In the transcripts
⌘K searches the full text of every recorded session — the decision you remember making but not where. It streams progress while it scans and reports how many sessions it covered, so a capped scan is visible as a cap.
Previewing what the work produced
Deliverables an agent hands back are collected as artifacts and previewable in place: Markdown, JSON, CSV as a table, images with zoom, PDFs, audio and video. The preview is read-only by design — editing always goes to a real app — and can widen to the full stage or sit as a side panel.
- Open in your default app, choose a specific app, or reveal it in Finder.
- Very long files preview their first several thousand lines and say so; binaries, oversized files and unsupported media say what to do instead of failing silently.
- Artifacts outside the workspace are refused rather than read — the preview honors the workspace boundary.
Exporting a conversation
A whole chat, or a single round, exports to a folder — text plus the images and files that went with it, bundled and packaged with progress while it works. This is the honest way to hand someone what happened: not a summary of the session, the session.
Something wrong or missing on this page? Tell us