The Local Knowledge Loop Starts With One Note

Knowledge workflows · By W.T. Roosevelt

A project can have a coding agent, a notes app, and a developer promoted to clipboard.

The decisions exist. The agent can read files. Yet each change of working surface begins with another explanation of the goal, the constraints, and the things already ruled out. That is the friction worth addressing before building an elaborate knowledge system.

The useful loop is small: bring the relevant note into the work, propose a change, inspect it, and keep the result where the next session can find it. The note remains a source to maintain, rather than a transcript to accumulate.

Give the connection a job

Claude Code can already read Markdown. A plugin needs to add a useful working experience beyond access to text.

Companion for Claude supplies an interface inside Obsidian: chat with note context, visible agent work, and proposed note edits that can be reviewed hunk by hunk. Its agent mode keeps writes behind confirmation. The value is the relationship between the source note, the proposed change, and the decision to keep it. Companion overview.

Start with a project note whose meaning you can check yourself. For example:

markdown
# Small project

## Goal
Build a personal reading list.

## Constraints
Keep the first version single-user. Do not add account registration.

## Next steps
Choose the smallest useful first screen.

Use this sample note for the exercise.

Install Companion through Settings → Community plugins → Browse → Companion for Claude, then enable it. Choose the model connection you intend to use, open the sample note, and enable the Note context chip.

In Agent mode, ask:

Propose a clearer next step for this project. Keep the single-user constraint and do not add account registration. Show the proposed note edit for review.

Read the proposed changes against the original note. Accept a useful hunk. Reject any hunk that changes the constraint or adds a commitment you did not make. Then inspect the resulting note: did the intended next step change while the constraint remained intact?

That last inspection is the useful result of the exercise. A fluent answer and a note you agree to maintain are different things. If the proposal is wrong, rejecting it is a valid outcome.

Keep the two working surfaces distinct

The same vault can support work in Obsidian and work from a terminal, with different integrations for each.

Companion's own in-app agent does not require MCP. On desktop, its Claude Code connection runs the installed claude command. For terminal-based vault workflows, the separate Obsidian Agent package uses the official Obsidian CLI by default. A specialized Companion MCP bridge remains available for clients that need its live-vault capabilities. These are related routes, rather than interchangeable names for one product. The desktop integration guide explains which path matches each client.

A first note-edit exercise does not require setting up every route. Establish the in-vault workflow you need, then add a terminal integration when there is a concrete task for it.

Review preserves a decision, not permanent correctness

A review step gives you a chance to choose the change. You still own deciding whether the note describes the project as it exists now. An accepted decision can become outdated; a well-written summary can omit something important. Keep the note small enough that you can recognize either problem.

Model access is also a separate choice. Companion supports a desktop Claude Code connection, your own Anthropic API credential, or an Ollama/OpenAI-compatible endpoint. Installing the plugin does not supply a model account or free API use. Attached note context is sent through the backend you select; a local vault does not by itself mean local inference. Setup and first workflows.

Try the loop on one sample project note: one useful proposed change, one review decision, and a final note you can explain. Expand from there when another real task justifies it.