The Open Framework for Building Agents
docs: add inbound links to orphaned pages (#1663)
Rich Hainesafe568887aa7
diff --git a/docs/concepts/security-model.md b/docs/concepts/security-model.mdindex b8d9229c0..717578df5 100644--- a/docs/concepts/security-model.md+++ b/docs/concepts/security-model.md@@ -103,3 +103,4 @@ Before exposing an agent to real traffic:- [Sandbox](../sandbox): backends, network policy, and brokering config- [Execution model and durability](./execution-model-and-durability): how durable sessions run- [Connections](../connections): static-token and OAuth connections+- [Responsible use](../responsible-use): deployer responsibilities and safeguards to review before productiondiff --git a/docs/guides/state.md b/docs/guides/state.mdindex 539131b92..a58ef5f45 100644--- a/docs/guides/state.md+++ b/docs/guides/state.md@@ -76,3 +76,4 @@ Every [subagent](../subagents) starts with its own fresh state, whether it's a b- Read state inside dynamic resolvers → [Dynamic capabilities](./dynamic-capabilities)- How step durability works → [Execution model & durability](../concepts/execution-model-and-durability)- The `ctx` accessors available alongside state → [TypeScript API](../reference/typescript-api)+- Tenant-scoped long-term memory in your own store → [Multi-tenant memory](../patterns/multi-tenant-memory)diff --git a/docs/schedules.mdx b/docs/schedules.mdxindex 10ca6cfe0..59e126cfe 100644--- a/docs/schedules.mdx+++ b/docs/schedules.mdx@@ -116,3 +116,4 @@ The gotcha is custom hosting. If you adapt the generated output to a process man- [Channels](./channels/overview): deliver schedule output to users.- [Sessions, runs & streaming](./concepts/sessions-runs-and-streaming): inspect a schedule run.+- [Dynamic scheduling](./patterns/dynamic-scheduling): manage schedule rows in your own store behind one dispatcher schedule.diff --git a/docs/tools/human-in-the-loop.md b/docs/tools/human-in-the-loop.mdindex a4c9cab13..d48d20edc 100644--- a/docs/tools/human-in-the-loop.md+++ b/docs/tools/human-in-the-loop.md@@ -125,3 +125,4 @@ From your own frontend, read the pending request off the latest message and answ- [Default harness](/docs/concepts/default-harness): the built-in tools, including `ask_question`- [Sessions, runs & streaming](/docs/concepts/sessions-runs-and-streaming): the event and resume contract behind the pause- [Building a frontend](/docs/guides/frontend/overview): render and answer requests from your own UI+- [Multi-tenant approvals](/docs/patterns/multi-tenant-approvals): resolve per-tenant approval policy for authored and connection tools