Write · Closed beta

Your agents already live in GitNow your knowledge does too

Edit Markdown in your Git repository. Give agents scoped access and review their proposals.

Open source
Self-hosted
MCP access

claude mcp add hanji --transport http http://localhost:4101/mcp --header "Authorization: Bearer YOUR_TOKEN"Run Hanji Write and create a scoped token first. Replace YOUR_TOKEN before connecting.

See how it works

Read. Review. Merge.

handbook / how-we-work.md

How we work

Ada · updated today

A shared handbook for product decisions, project notes, and team guides.

HandbookMarkdownGit-backed

Record a decision

Describe the problem and the options.
Choose an owner and a next step.

Make it easy to find

Link new guides from this handbook.

MCP / THE SAME PAGE

→ hanji_read
handbook/how-we-work.md

# How we work

A shared handbook for product decisions, project notes, and team guides.

## Record a decision
- Describe the problem and the options.
- Choose an owner and a next step.

## Make it easy to find
Link new guides from this handbook.
Give the next person a place to start.

Plain text. Only what you’ve granted.

Interactive example · try Merge⑂ main · handbook/how-we-work.md

Request access

Try Hanji with us

Write is in closed beta, with access by request. Contact us to tell us how you would like to use it. The handbook is open to everyone.

Explore the live handbook

Already have access? Setup notes

Requirements
An existing Write checkout, recent Node.js, pnpm, Git, a C build toolchain, and a folder of Markdown. No model account is needed to read or edit.
Local setup
From the checkout, install dependencies and start the web app. Open localhost:4100.
```
pnpm install
pnpm dev:web
```
First workflow
Name your space, choose an owner password, and select your Markdown folder. Edit one page and press Update: your first change is saved in Git.
Agent connection
Connect your coding agent with a scoped token when needed. Your agent account or subscription is managed separately. See the deployment options below for connection details.

More setup options

MARKDOWN EDITOR

Edit Markdown.
Keep clean Git diffs.

Make a focused edit without rewriting the rest of the document.

WHAT YOU EDITdecisions.md

Make the ~~next~~ right thing
easy to find.

One word changed. Update.

WHAT GIT SEES+1 −1

− Make the next thing easy to find.
+ Make the right thing easy to find.

Ada · Update decisions.md

How byte-preserving edits work

AGENT PROPOSALS

Review the diff.
Approve the change.

Agents propose edits on a branch. Review the proposal branch’s diff before merging; the changes reach your pages only after merge.

claudeClarify the review owner+2 −0

Added an owner so each incident review has someone responsible.

+ ## Review owner+ The incident lead writes the review and shares it with the team.

INDEPENDENT OF ANY MODEL

NO BUILT-IN AI METERING

Built for agents.
Runs without one.

Reading, editing, and publishing do not require a model account or API key. Connect your own agents when they are useful, with access limited to the content you choose.

Any agent subscription or model usage is handled separately by your provider.

0 bundled models0 AI credits100% your Markdown

A NOTE TO READING AGENTSRead the handbook in a text format for agents.llms.txt

ACCESS CONTROL

Set permissions.
For people and agents.

Control which pages people and agents can access.

Select a reader to preview their access.

FIELDNOTES / PAGES4 visible

How we workhandbook / how-we-work.mdEveryone

Architectureengineering / architecture.mdTeam + agent

The next chapterplanning / next-chapter.mdAda + Remy

A work in progressprivate / rough-thoughts.mdOnly Ada

Ada owns this workspace. All four pages are visible.

Hanji Write controls app access. Repository access still exposes the files.

COMMENTS & HISTORY

Discuss changes.
Track contributions.

Comment on a page. See who changed it.

FROM THE HANDBOOK

Open the note in the margin.

Page comments.
Stored outside Git.

Comments stay out of git. Agents read them only with permission.

Read about comments

THE PAPER TRAIL

People above. Agents below. Eight weeks of work.

People Agents

8 weeks agoToday

A quiet day writes nothing at all.

CHOOSE YOUR WORKFLOW

Find the right tool
for your knowledge.

Compare the workflows each tool is designed to support.

Compare Hanji Write’s purpose, content, git workflow, and agent access with other knowledge tools.
What matters to you?	Hanji WriteYOUR KNOWLEDGE, YOUR GIT	ObsidianTHE PERSONAL VAULT	NotionTHE ALL-IN-ONE	ConfluenceTHE TEAM WIKI · CLOUD	GitBookTHE DOCS SITE
Made for	Teams + their agents	Personal knowledge	Docs + projects + databases	Atlassian-connected teams	Published documentation
Your content	Markdown files	Markdown files	Pages + databases	Pages + spaces	Docs + optional Git Sync
Git’s role	The source of truth	Bring your own workflow	Markdown via export	Content via export	Two-way repository sync
Agent access	Scoped MCPEdits proposed as git diffs	Local filesConnect your own tools	Notion MCPConnect external assistants	Rovo MCPConnect external assistants	Published-site MCPDocs for agent readers
Keep in mind	Early. Self-hosted.SSO + hosted service still ahead	Shared vault, shared access.No per-page grants in Sync	The workspace is Notion.Markdown is an export	The workspace is Confluence.Not a Markdown repository	Publishing comes first.A different focus from Hanji Write

Choose the workflow that fits your team.

Find your fit

Sources & scope Checked September 9, 2026

Our assessment of fit, based on the official documentation below. Confluence refers to Cloud. Features and access can depend on plan and configuration; extensions can add other workflows.

Hanji Write: Current status · People and agents
Obsidian: Files and team sync · Shared-vault permissions
Notion: Wikis and databases · Exports · MCP
Confluence: Features · Exports · Rovo MCP
GitBook: Two-way Git Sync and MCP

DEPLOYMENT

Run locally.
Share on your terms.

Local. Shared. Published. Your choice.

Closed beta

01Just you, locally

Start Hanji Write, name your workspace, set an owner password, and select the folder containing your Markdown files.

Write is in closed beta, with access by request. Contact us to tell us how you would like to use it. The handbook is open to everyone.

# From an existing source checkout
pnpm install && pnpm dev:web

Write setup notes

02Your team, on a tailnet

One shared instance where the network signs people in. Nobody types a password. Their permissions stay exactly as you set them.

export HANJI_TAILSCALE_OWNER=you@github
next start -H 127.0.0.1 -p 4100
tailscale serve --bg 4100

Run on your tailnet

03With your coding agents

Give agents scoped read access through MCP or HTTP. Proposed edits arrive on a branch for you to review and merge.

pnpm hanji token my-claude notes=read+propose
# Connect your agent with the returned token.

Configure agent access

04Published to the web

Everything you’ve opened to everyone, as a static website. A Markdown mirror and llms.txt come along. The handbook is published this way.

pnpm hanji rule handbook everyone-read
pnpm hanji export ./site

Publish selected content

RELEASE UPDATES

Follow the development.
Hear about new releases.

Receive occasional updates on development progress and release availability.

Read the Write handbook

Your agents already live in GitNow your knowledge does too

How we work

Record a decision

Make it easy to find

Try Hanji with us

01Requirements

02Local setup

03First workflow

04Agent connection

Edit Markdown.Keep clean Git diffs.

Review the diff.Approve the change.

Built for agents.Runs without one.

Set permissions.For people and agents.

Discuss changes.Track contributions.

Find the right toolfor your knowledge.

Run locally.Share on your terms.

Follow the development.Hear about new releases.

Requirements

Local setup

First workflow

Agent connection