Mintlify’s self-updating documentation system uses two cooperating agents: a background agent that tunes the setup and runner agents that act when a trigger fires. Triggers can be schedules, code merges, or events in tools such as Jira; runners use skills to produce documentation changes, usually as pull requests, and notify reviewers. The background agent reviews run histories, integrations, platform analytics, and PR acceptance to adjust triggers, skills, and shared memory. For example, after code-merge-triggered CLI documentation changes were repeatedly rejected because the CLI ships continuously, it moved that work to a monthly release-notes schedule. The system has raised the internal acceptance rate for documentation PRs from 70% to 90%.
The central design choice is structured, git-backed memory rather than relying mainly on free-form notes. JSON schemas capture release details, stakeholders, review preferences, relevant discussions, style guidance, users, and integration data, making context more dependable and easier to evaluate. Mintlify built its own agent harness with tools for subagents, session forking, memory compaction, skills, and sandboxed shell commands; in offline tests it performed similarly to Pi while using 50% fewer tokens. Run logs and outputs are stored as JSON, with forked sessions recorded as a tree so complete histories can be reconstructed. The architecture also supports updates to customer setups: background agents receive instructions about schema or product changes, audit for regressions, and can decide which customers and contacts are appropriate for new features.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.