terminal markdown viewer for agent workflows
A better agentic feedback flow.
Your agent writes a spec. You comment on the exact section, inline. The agent reads it instead of long conversation chunks.
You just left a comment. Now the agent can read it.
inspiration and friends
“If herdr, hunk, and agentation had a baby.”
mdtation combines ideas and flows from a few great tools.
feedback, the problem today
Agents ask for feedback in the worst possible places
To get the best agentic results, we give our agents feedback: on their plans, their findings, their drafts. But the conversational flow and picker tools are slow and clunky. The mdtation flow is more natural, and still terminal friendly.
Review the plan, not the chat.
Specs, plans, drafts, reviews: the prose around the code deserves the same review flow as the diff.
- 1
The agent writes a file
Ask for the plan as a markdown file, not an ephemeral conversation. A file is something you can open again tomorrow. A conversation gets messier.
mdtation plans/auth.md
- 2
You read, comment, and copy
Press
con a line, or drag-select a sentence, and write what is wrong.Ccopies it as a reference: line, section, quote, note.c, then C - 3
The agent revises, you loop
The agent reads the report and edits the file. Open it again: your comments are still anchored. Archive what landed, go again.
mdtation plans/auth.md list
What lands on the clipboard Line, section path, quote, note. Plain text, no schema to learn.
Line 41 Auth / Session refresh
Refresh tokens are rotated on every request and the old token is
revoked immediately.
> Immediate revoke breaks parallel requests from the same tab. Keep a 30 s grace window, then revoke.Line 58 Auth / Logout
Logout clears the cookie and does nothing server-side.
> Also revoke the refresh token, otherwise the cookie is the only thing keeping the session out.built for agents
Paste it into any agent
Plain markdown with a line number, a heading path, the passage and your note. For a whole review, mdtation file.md list prints every comment as one report.
Read the comments I left on plans/auth.md by running `mdtation plans/auth.md list`. Address each one in order, then rewrite the file in place. Keep the headings so my remaining comments stay anchored.
Everything a viewer should have had
Menu bar, command palette, settings. View toggles are remembered.