Local-first agent conversation workspace

Branch agent conversations into knowledge you own.

A browser interface on localhost for branching from exact response blocks and preserving every path as a durable plain-file Knowledge Tree.

See how it works View on GitHub

Select an exact block. Branch once, twice, or deeper—every child keeps one route back.

Pull the first thread

01 / Addressable blocks

Every response has places to branch.

Agent responses are organized into addressable Markdown blocks. Choose a whole block to begin the next request from that exact point.

Lineage App branch composer anchored to the response block about creating a shared cooling hub — The branch starts at one addressable idea.

02 / Isolated lineage

A child keeps the path, not its siblings.

The child thread preserves root-to-fork context, then continues independently. Content from sibling branches stays out.

A child conversation titled Library porch cooling hub showing faded parent context above its Current branch divider — Parent context above. An isolated child thread below.

03 / Bird's-eye map

You changed direction. The map kept both.

Trace every branch, return to a node, branch again, and open conversations directly from the Knowledge Tree.

The Lineage App Knowledge Tree connecting seven cooling-plan conversations across three branches — Seven conversations. One navigable tree.

04 / Ownership

The interface is a view. The files are yours.

Markdown stores conversations; YAML stores relationships. Local Git records each mutation, while AGENTS.md and a regenerated index keep the vault traversable.

The Files view showing the local public-demo vault, thread Markdown, YAML metadata, and nested branch folders — Markdown for the conversation. YAML for the graph.

Stored locally Readable files. Git-backed history. Your graph.

Quickstart

Run Lineage App on trusted localhost.

Start after cloning or downloading the repository and preparing the host machine.

Bring the prerequisites

Git, Python 3.11+, Node.js 22+, a modern browser, and GitHub Copilot CLI with active access.

The Bash launcher supports macOS and Linux-style environments today.

Authenticate once

copilot login

Lineage App uses the installed CLI and the models available to your Copilot account.

Start the local workspace

./scripts/run-local.sh

The launcher installs project dependencies, builds, binds localhost, and opens the browser.

Data defaults to ~/web-context-graph-data/. Set WCG_VAULT_ROOT before launching to choose another directory.

Open the full Quickstart

FAQ

Know the boundaries before you branch.

What works today, what stays local, and what is deliberately not implied.

What exactly is Lineage App?

A trusted, single-user, local-first browser workspace for branching GitHub Copilot CLI conversations at addressable response blocks and preserving the resulting lineage as a plain-file Knowledge Tree.

Is it a desktop app or hosted service? What works today?

Neither. FastAPI serves the React UI on localhost; the host machine runs the backend and agent. The Bash launcher supports macOS and Linux-style environments. There is no supported native-Windows launcher or hosted multi-user service.

Which agents, models, and providers are supported?

GitHub Copilot CLI only today, invoked directly as a subprocess. Lineage App is not provider-neutral, and model availability comes from your Copilot CLI account.

What do I need before starting?

Git, Python 3.11+, Node.js 22+, GitHub Copilot CLI with active access and authentication, and a modern browser on a macOS or Linux-style environment.

Does the one-command launcher install everything?

No. After prerequisites, clone/download, and Copilot authentication are ready, it handles project dependencies, the production build, localhost startup, and opening the browser. It does not install system tools or provide Copilot access.

Where is my data, and how do I choose the directory?

The default is ~/web-context-graph-data/. Set WCG_VAULT_ROOT before launching to use another directory.

Does it sync to GitHub?

Not automatically. Every mutation is committed to local Git. You can configure and push a remote manually; a private repository is recommended for sensitive conversations.

Why not use NotebookLM or an LLM wiki?

NotebookLM is excellent for source-grounded synthesis, while LLM wikis can compile documents into useful pages and links. Lineage App solves a different problem: keeping you in control while knowledge is explored.

Every branch is a deliberate choice; its parent and fork point remain visible, sibling contexts stay isolated, and the complete tree remains inspectable as local Markdown, YAML, and Git history. It does not make AI infallible - it makes the path from question to answer auditable, revisable, and yours. The tools can complement one another.

Can another agent harness consume the vault?

Yes. AGENTS.md documents discovery through the regenerated index, authoritative relationships in meta.yaml, conversation content in thread.md, and root-to-current reconstruction without sibling leakage.

Is it safe to expose publicly?

No. Keep it on trusted localhost. Copilot runs with broad local tool access and --no-remote; the backend is not hardened for public or multi-user access.

Is highlighted-text branching supported?

No. Responses are addressable at the Markdown block level today. Arbitrary highlighted spans are future work.

Is it free and open source?

The source is licensed under GNU AGPL-3.0-or-later. Copilot access, usage, subscription, and billing remain governed separately by GitHub.

The next node is yours

Craft your first three today, one branch at a time.

Clone, authenticate Copilot CLI, then launch on macOS or Linux with Git, Python 3.11+, Node.js 22+, and a modern browser ready.

Start with Quickstart View source Contact Jorge