Sib: Git-based LLM client replaces SQLite with version control

Sib reimagines LLM conversation storage by treating conversations as version-controlled artifacts rather than database records. Instead of building separate features for undo, branching, backup, and sharing—as most LLM clients do—Sib achieves all of them through Git's native capabilities. A conversation is a linear chain of commits, each containing a JSON object with role (user or assistant), content, and metadata. When you ask a prompt, Sib reads the entire chain from HEAD, sends it to the LLM endpoint, and records both the user turn and assistant response as two new commits. This design naturally supports forking (by choosing a parent commit other than HEAD), editing (by creating a new branch from an earlier point), and sharing (by pushing to any Git remote).

The creator built Sib around a deliberate philosophy: rather than shipping each capability as a named feature, let users control context the way Git does. The `-p` flag switches the parent commit, the `-r` flag skips stdin to move HEAD without an API call, and the `-n` flag starts a fresh chain—simple flags that compose into powerful workflows. Named saves (e.g., `sib save eva-3.0-go-off`) let users label important conversation points without memorizing commit hashes. The project is explicitly in early stages; the codebase is not yet stable for large feature work, but the creator invites involvement in shaping the core API.