Non-code projects
Splitkick is git-backed, not code-only. Anything in a git repository works: an Obsidian vault, a documentation folder, a data directory, a research project.
Why worktrees for documents
An agent rewriting twenty Markdown files is as risky as one rewriting twenty source files. In a worktree the rewrite is a branch: read the diff, keep it or drop it. Several agents can draft alternatives in parallel.
See the output
The pane next to the chat shows what the agents produce:
- Markdown and text render in the pane.
- Images open inline in the answer and in a zoom viewer (pinch, double-tap or scroll to zoom).
- PDFs and video open in the pane.
- HTML and web pages open in the embedded browser.
- Every file path an agent writes in an answer is a link, including
~/,../and paths with spaces. A path that does not exist is marked with "?". Reveal in Finder is one click away.
Limits today
- The project must be a git repository. Plain folders with snapshots are on the roadmap.
- Large binary files follow the normal git rules; use Git LFS where you would anyway.