Add the /docs/deep-agents website library - #937
Merged
Conversation
Six pages: a getting-started introduction that consolidates the one setup story (a Deep Agents graph is a LangGraph graph, so @threadplane/langgraph is the whole client wiring), plus one page per middleware capability — planning, filesystem, subagents, memory, skills. Each capability page covers what the cockpit demo shows and how the capability reaches the UI, sourced from the rebuilt deepagents 0.7.11 group. The private-state constraint on memory_contents and skills_metadata is stated on both pages it affects rather than worked around quietly. Rewires the six deep-agents docs-links sentinels to real targets, so COCKPIT_TOPICS_WITHOUT_DOCS is now empty and the guard's blanked-entry assertion forbids blanking anything. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…deep-agents intro Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
blove
enabled auto-merge (squash)
September 1, 2026 20:47
This was referenced Sep 1, 2026
blove
added a commit
that referenced
this pull request
Sep 1, 2026
…untimes The cockpit -> docs direction shipped with both libraries (COCKPIT_DOCS_LINKS covers all six deep-agents entries and all four runtimes entries), but the reverse table only knew the five first-iteration pages. Every deep-agents page (#937) and every runtimes page (#913) sent its Run/Code/API buttons to Cockpit home instead of the demo the page describes. Add the 16 missing entries: - deep-agents: the five capability pages map to their core-capabilities topic; the introduction maps to deep-agents/getting-started/overview. - runtimes: all three pages of each runtime section (overview, quickstart, how-it-connects) map to that runtime's one demo, since a single demo serves them equally well; the introduction maps to runtimes/getting-started/overview. Also add deep-agents and runtimes to AnalyticsLibrary. Without it every handoff from these two libraries would have been attributed to 'unknown', so the new links would be invisible in the funnel they exist to feed. Each of the ten destination URLs was checked against production and returns a hard 200. The check discriminates: an unknown topic 307s to the fallback and an unknown product 500s, so the 200s are real pages rather than SPA soft-200s. Tests: the exact pin is updated, plus four guards — every key names a page that exists in docs-config (a typo'd key is otherwise invisible: the page just keeps the Cockpit-home fallback), the deep-agents/runtimes links round-trip against COCKPIT_DOCS_LINKS, the analytics library is no longer 'unknown', and each runtime section's three pages resolve to the same demo. All four were mutation-tested to confirm they fail when the mapping is wrong. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
blove
added a commit
that referenced
this pull request
Sep 1, 2026
…untimes The cockpit -> docs direction shipped with both libraries (COCKPIT_DOCS_LINKS covers all six deep-agents entries and all four runtimes entries), but the reverse table only knew the five first-iteration pages. Every deep-agents page (#937) and every runtimes page (#913) sent its Run/Code/API buttons to Cockpit home instead of the demo the page describes. Add the 16 missing entries: - deep-agents: the five capability pages map to their core-capabilities topic; the introduction maps to deep-agents/getting-started/overview. - runtimes: all three pages of each runtime section (overview, quickstart, how-it-connects) map to that runtime's one demo, since a single demo serves them equally well; the introduction maps to runtimes/getting-started/overview. Also add deep-agents and runtimes to AnalyticsLibrary. Without it every handoff from these two libraries would have been attributed to 'unknown', so the new links would be invisible in the funnel they exist to feed. Each of the ten destination URLs was checked against production and returns a hard 200. The check discriminates: an unknown topic 307s to the fallback and an unknown product 500s, so the 200s are real pages rather than SPA soft-200s. Tests: the exact pin is updated, plus four guards — every key names a page that exists in docs-config (a typo'd key is otherwise invisible: the page just keeps the Cockpit-home fallback), the deep-agents/runtimes links round-trip against COCKPIT_DOCS_LINKS, the analytics library is no longer 'unknown', and each runtime section's three pages resolve to the same demo. All four were mutation-tested to confirm they fail when the mapping is wrong. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
blove
added a commit
that referenced
this pull request
Sep 1, 2026
…untimes The cockpit -> docs direction shipped with both libraries (COCKPIT_DOCS_LINKS covers all six deep-agents entries and all four runtimes entries), but the reverse table only knew the five first-iteration pages. Every deep-agents page (#937) and every runtimes page (#913) sent its Run/Code/API buttons to Cockpit home instead of the demo the page describes. Add the 16 missing entries: - deep-agents: the five capability pages map to their core-capabilities topic; the introduction maps to deep-agents/getting-started/overview. - runtimes: all three pages of each runtime section (overview, quickstart, how-it-connects) map to that runtime's one demo, since a single demo serves them equally well; the introduction maps to runtimes/getting-started/overview. Also add deep-agents and runtimes to AnalyticsLibrary. Without it every handoff from these two libraries would have been attributed to 'unknown', so the new links would be invisible in the funnel they exist to feed. Each of the ten destination URLs was checked against production and returns a hard 200. The check discriminates: an unknown topic 307s to the fallback and an unknown product 500s, so the 200s are real pages rather than SPA soft-200s. Tests: the exact pin is updated, plus four guards — every key names a page that exists in docs-config (a typo'd key is otherwise invisible: the page just keeps the Cockpit-home fallback), the deep-agents/runtimes links round-trip against COCKPIT_DOCS_LINKS, the analytics library is no longer 'unknown', and each runtime section's three pages resolve to the same demo. All four were mutation-tested to confirm they fail when the mapping is wrong. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
blove
added a commit
that referenced
this pull request
Sep 1, 2026
…untimes (#938) The cockpit -> docs direction shipped with both libraries (COCKPIT_DOCS_LINKS covers all six deep-agents entries and all four runtimes entries), but the reverse table only knew the five first-iteration pages. Every deep-agents page (#937) and every runtimes page (#913) sent its Run/Code/API buttons to Cockpit home instead of the demo the page describes. Add the 16 missing entries: - deep-agents: the five capability pages map to their core-capabilities topic; the introduction maps to deep-agents/getting-started/overview. - runtimes: all three pages of each runtime section (overview, quickstart, how-it-connects) map to that runtime's one demo, since a single demo serves them equally well; the introduction maps to runtimes/getting-started/overview. Also add deep-agents and runtimes to AnalyticsLibrary. Without it every handoff from these two libraries would have been attributed to 'unknown', so the new links would be invisible in the funnel they exist to feed. Each of the ten destination URLs was checked against production and returns a hard 200. The check discriminates: an unknown topic 307s to the fallback and an unknown product 500s, so the 200s are real pages rather than SPA soft-200s. Tests: the exact pin is updated, plus four guards — every key names a page that exists in docs-config (a typo'd key is otherwise invisible: the page just keeps the Cockpit-home fallback), the deep-agents/runtimes links round-trip against COCKPIT_DOCS_LINKS, the analytics library is no longer 'unknown', and each runtime section's three pages resolve to the same demo. All four were mutation-tested to confirm they fail when the mapping is wrong. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Builds the
/docs/deep-agents/docs library, mirroring the/docs/runtimes/pattern from #913, and rewires the six deep-agents cockpit capabilities from the "no published docs page" sentinel to real targets.Pages
Six MDX pages, ~4,000 words total.
getting-started/introduction— what the Deep Agents framework is (LangChain's agent harness: five capabilities as LangGraph middleware), that the cockpit group runs the realdeepagentspackage at 0.7.11, and the one consolidated setup story. A Deep Agents agent is a LangGraph graph, so@threadplane/langgraphwithprovideAgent()/injectAgent()is the whole client wiring; the page links the LangGraph quickstart rather than re-teaching it, which replaces the boilerplate that was previously repeated in every capability guide.capabilities/planning—TodoListMiddleware,todoson the state, the panel as acomputed()overvalue('todos').capabilities/filesystem—FilesystemMiddlewarewithStateBackend, the file tree fromvalues.files, andFilesystemPermission(mode="interrupt")surfacing through the standard chat interrupt panel with a{ decisions: [{ type: 'approve' }] }resume payload.capabilities/subagents—SubAgentMiddleware'stasktool lighting the subagent cards natively, because['task']is already the tracker's defaultsubagentToolNames. Parallel fan-out attributes by exact namespace match.capabilities/memory—MemoryMiddlewarewithStoreBackendand a cross-thread/memories/AGENTS.md.capabilities/skills—SkillsMiddleware,SKILL.mdprogressive disclosure against the agentskills.io spec, and theCompositeBackendprefix-stripping trap.The private-state constraint is stated rather than hidden:
memory_contentsandskills_metadataare annotatedPrivateStateAttr, so they never appear in the streamedvalues. Both pages say plainly that the demo's custom-event republishing is an application-side shim, not a framework feature, and that without it the panel still fills in — just at settle rather than live.Wiring
docsConfiggains adeep-agentslibrary (getting-started+capabilitiessections);LibraryIdand theLibraryMarkglyph map are extended in step./docs/runtimesis surfaced.COCKPIT_DOCS_LINKSpoints all six deep-agents capabilities at real pages, soCOCKPIT_TOPICS_WITHOUT_DOCSis now empty. The list stays: with an empty list, the guard's blanked-entry assertion forbids blanking anything at all.cockpit-shell.spec.tsxgains a positive assertion that a deep-agents capability links at the new library, and its no-link test now drives the sentinel through a presentation override rather than through a table entry that happens to be blank.Verification
apps/website: 447/447 vitest green, including docs, sitemap-dates, and structured data. The MDX was committed before the final run, per the sitemap-dates git-history requirement.apps/cockpit: 422/422 green.cockpit-registrygreen./docs/deep-agents/capabilities/skillzfailed two independent assertions — the on-disk content-tree check and the descriptor cross-check — and both went green again on restore.libraryIntroPath(), and every one of the 15 internal hrefs across the new MDX returns 200.🤖 Generated with Claude Code