DocsAlot turns scattered help center articles, knowledge base, and developer docs into one source of truth for humans and AI agents. It includes hosted MCP, llms.txt, and skill.md. Your docs show up in AI answers, onboarding gets faster, and agents stop reading stale context.
Write, structure, and publish technical documentation in a visual editor with Markdown mode, AI-assisted edits, reusable components, and version history.
the human-approval gate before publishing makes sense. what happens on the other side of that though - if an agent proposes a doc update through the CLI/MCP and a human edits or rejects most of it before saving, does the agent see what changed and why, or does it just try again from scratch next time with no memory of the correction?
@new_user_2790a57d4d that covers the "what changed" half nicely. still curious about the "why" - does the diff carry any signal about the reason for the edit, or is it just the raw before/after text, so the agent has to infer intent on its own next time?
You know this really addresses a genuine issue. its such a hassle to keep documents updated in multiple locations and the fact that they can alsoo be useful for AI agents is a huge bonus. i absolutely love the concept of having a single source of truth.
Dial
the human-approval gate before publishing makes sense. what happens on the other side of that though - if an agent proposes a doc update through the CLI/MCP and a human edits or rejects most of it before saving, does the agent see what changed and why, or does it just try again from scratch next time with no memory of the correction?
DocsAlot
@galdayan everything is version controlled, so the agent will see that a new version was created by a human or even another agent.
Dial
@new_user_2790a57d4d that covers the "what changed" half nicely. still curious about the "why" - does the diff carry any signal about the reason for the edit, or is it just the raw before/after text, so the agent has to infer intent on its own next time?
DocsAlot
@galdayan oh right, yes you are correct. It doesn't communicate the reasoning back to the agent. That is actually a really good feature.
We have to ask for the humans, the reasons for rejection that can be propagated back towards the agent.
Let me think of a good UX for this. Thanks again.
Feel free to dm, me on linkedin if you have any more thoughts about this. https://www.linkedin.com/in/eff-kay/
You know this really addresses a genuine issue. its such a hassle to keep documents updated in multiple locations and the fact that they can alsoo be useful for AI agents is a huge bonus. i absolutely love the concept of having a single source of truth.
DocsAlot
@liam_ward2 appreciate it Liam, yes, its a non-trivial problem. Would love for you to try it out, any feedback is appreciated .
Softorino 💻📲
Writing help docs, the useful bit is the step someone got stuck on. Typing it yourself is the only way that detail survives into the page.
DocsAlot
@yelyzaveta_kibets thanks lisa, appreciate it.