remziduzagac/slipbox

Read, review and edit what your coding agent writes, in your terminal.

Keep documents readable while making focused edits with the lens. Use slipbox on your own notes and code too, and add agent integration when it helps.

slipbox sits beside Claude Code, Codex, or any agent that runs shell commands. Follow an idea from the first plan to the code that implements it. Read comfortably, review what changed, and make edits of your own. Tables fit the window, and code is highlighted. Pictures, diagrams and maths sit alongside your writing. Themes, keys and settings make it yours.

Editing is intuitive yet innovative. The lens opens the Markdown around your cursor for editing, while the rest stays rendered. Stay where you were reading, keep the surrounding document in view, and focus on the change.

The editor is necessary and sufficient. It has the everyday editing tools, from selections, undo and find-and-replace to completion, language servers, linters and spelling. Your own editor is a key away whenever you want more.

Use the arrow keys and the shortcuts you know from other editors, or vim’s keys, and discover the rest as you go. space opens a menu of actions, ? shows every key, and : opens the command palette. Everything is clickable too.

An agent works on saved files through slipbox’s command line and bundled skill. It searches, follows links and makes changes. A write guarded with --if-unchanged refuses to replace a file changed since the agent read it. What the agent saves appears at once. If a file changes while you have unsaved edits, slipbox asks what to keep.

Gather references and excerpts in the scratch, each with its file path and line numbers. Build your next prompt while keeping your document focused.

Review what the agent changed, in git. A note’s diff shows each paragraph before and after, with the words that changed marked, and a code file’s sits side by side. Keep, revert or send back each change, one at a time. Settle a merge’s conflicts on a merge screen, and see which links a merge would break before you make it.

Open the folder you already have: a repository, an Obsidian vault, a zk notebook or an ordinary folder. Opening it writes nothing there. Your notes and code stay in their files, alongside the tools you already use.