Hosted preview · Open source

Keep what
agents learn.

A workspace for plans, investigations, benchmarks, and handoffs that should outlive chat—not live forever in Git.

  • SSH-native
  • Project-scoped
  • Human-readable

THE MESSY MIDDLE

Useful now.
Not permanent.

Coding agents create a trail of useful intermediate knowledge. Most of it matters for days or weeks—not forever.

Chat makes that context fragile. Git makes it permanent. docs-ssh gives it a project-scoped place to stay until the work is done.

01
CHATEasy to lose

Fast, conversational, and hard to recover next week.

02
DOCS-SSHDurable for now

Searchable, scoped, and deliberately outside the repository.

03
GITBuilt to last

The right home for durable decisions and maintained docs.

ONE WORKSPACE, TWO VIEWS

Shell-native for agents.
Legible for people.

01

Agents write over SSH

Use familiar operations like find, rg, and small range reads. No custom client required.

02

Context stays scoped

Each workspace and project gets a stable boundary for notes, tasks, issues, and handoffs.

03

Humans browse the same files

Review what an agent learned without opening a terminal or digging through a chat transcript.

$ npx docs-ssh@latest login --host docs-ssh --viewer-origin https://docs.trknhr.dev

WHAT LIVES HERE

The artifacts around
the artifact.

The work that helps ship the code, without becoming part of the codebase forever.

01 / PLAN

Implementation
plans

Decisions, sequencing, and the path an agent intends to take.

02 / TRACE

Investigation
notes

What was checked, what failed, and which clues mattered.

03 / RESULT

Benchmark
results

Temporary evidence that informs a decision without living forever.

04 / NEXT

Task
handoffs

A clear starting point for the next agent, session, or person.

DESIGN QUESTIONS

Small interface.
Deliberate choices.

Read the full design article
Why not just use Git?

Git remains the right place for maintained documentation and durable decisions. docs-ssh is for intermediate work that is valuable now but likely to become stale.

Why SSH?

Agents already know filesystem operations. SSH makes those operations remote, authenticated, scriptable, and easy to inspect without introducing a project-specific protocol.

Why not MCP or RAG?

They solve different layers. MCP can expose tools and RAG can retrieve from a corpus. docs-ssh focuses on where short-lived project knowledge lives and how both agents and humans access it.

Can I self-host it?

Yes. The server is open source under Apache-2.0. The hosted preview simply offers a managed place to try the same model.

MAKE CONTEXT LAST LONG ENOUGH

Give useful work
somewhere to land.

Try the hosted preview, or run docs-ssh on infrastructure you control.

Sign in to hosted beta View source on GitHub