Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/deploy/deploy-your-agents.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Once you've wrapped your agent with the Agent Stack server, you need to containe
## Prerequisites

- Docker installed and running (or use GitHub Actions via template)
- Agent wrapped with Agent Stack SDK ([Wrap Existing Agents](/deploy/wrap-existing-agent) or [Build New Agent](/deploy/build-new-agent))
- Agent wrapped with Agent Stack SDK ([Wrap Existing Agents](/deploy/wrap-existing-agents) or [Build New Agent](/introduction/start-building-agents))
- Agent Stack installed ([Quickstart](/introduction/quickstart))

## Containerize Your Agent
Expand Down Expand Up @@ -142,7 +142,7 @@ agentstack build . --dockerfile=./deploy/Containerfile --import
Now that your agent is deployed, enhance it with extensions:

<CardGroup cols={2}>
<Card title="LLM Service" icon="rotate" href="/extensions/llm-service">
<Card title="LLM Service" icon="rotate" href="/extensions/llm-proxy-service">
Change your agent's LLM at runtime and manage model connections dynamically
</Card>

Expand Down
2 changes: 1 addition & 1 deletion docs/extensions/agent-settings.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Sometimes you need to give users control over how your agent behaves during a co
The Agent Stack platform provides a Settings extension that creates an interactive UI component where users can configure these options before or during their interaction with your agent.

<Tip>
Settings extensions are a type of [Platform Extension](/concepts/extensions) that allows you to easily "inject dependencies" into your agent. This follows the inversion of control principle where your agent defines what it needs, and the platform provides those dependencies.
Settings extensions are a type of [Service Extension](/sdk/overview#dependency-injection-service-extensions) that allows you to easily "inject dependencies" into your agent. This follows the inversion of control principle where your agent defines what it needs, and the platform provides those dependencies.
</Tip>

## Quickstart
Expand Down
118 changes: 0 additions & 118 deletions docs/extensions/overview.mdx

This file was deleted.

6 changes: 3 additions & 3 deletions docs/extensions/rag.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -342,6 +342,6 @@ async def rag_agent(
### Next steps
To further improve the agent, learn how to use other parts of the platform such as LLMs,
file uploads and conversations:
- [LLM extension](./llm-configuration)
- [Multi-turn conversations](./multi-turn)
- [File handling](./file-handling)
- [LLM extension](/extensions/llm-proxy-service)
- [Multi-turn conversations](/guides/multi-turn)
- [File handling](/guides/files)
2 changes: 1 addition & 1 deletion docs/introduction/connect-a2a-agents.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ That's it! Your agent is now registered with Agent Stack and accessible through
The proxy creates a bridge between your A2A agent and Agent Stack by:

1. **Intercepting agent card requests** - Captures `/.well-known/agent-card.json` requests from any A2A client
2. **Adding Agent Details extension** - Automatically injects the necessary [AgentDetail](/build-agents/agent-details) extension data that enables the agent to work within the Agent Stack ecosystem
2. **Adding Agent Details extension** - Automatically injects the necessary [AgentDetail](/extensions/agent-details) extension data that enables the agent to work within the Agent Stack ecosystem
3. **Auto-registration** - Automatically registers the modified agent with the Agent Stack, making it immediately available

<Note>
Expand Down