Skip to content

Commit dd48b04

Browse files
docs: revise migration guide for agent stack installation (#1435)
Updated migration guide for users, agent builders, and self-hosting instructions for the new Agent Stack. Signed-off-by: Jenna Winkler <[email protected]>
1 parent 9aa9634 commit dd48b04

File tree

1 file changed

+24
-9
lines changed

1 file changed

+24
-9
lines changed

apps/beeai-web/src/modules/blog/posts/introducing-agent-stack.mdx

Lines changed: 24 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -95,43 +95,58 @@ Then check out our [Quickstart Guide](https://docs.beeai.dev/introduction/quicks
9595

9696
## Migration Guide
9797

98-
### For Users
98+
The steps below cover all user types, whether you’re running locally, building agents, or hosting your own stack.
9999

100-
1. Uninstall the old platform:
100+
### If You Run It Locally
101+
102+
If you were using the old BeeAI Platform CLI or local server, you’ll just need to reinstall and switch to the new
103+
command prefix.
104+
105+
1. Uninstall the old version
101106

102107
```
103108
beeai self uninstall
104109
```
105110

106-
2. Install Agent Stack:
111+
2. Install Agent Stack
107112

108113
```
109114
sh -c "$(curl -LsSf https://raw.githubusercontent.com/i-am-bee/agentstack/HEAD/install.sh)"
110115
```
111116

112-
3. CLI command change:
117+
3. Use the new CLI
113118

114119
```
115120
agentstack [OPTIONS] COMMAND [ARGS]
116121
```
117122

118-
### For Agent Builders
123+
All previous beeai commands now use the agentstack prefix.
124+
125+
### If You Build Agents
119126

120-
**All container images will need to be rebuilt to apply the appropriate changes.**
127+
If you’ve built agents that run on BeeAI Platform, you’ll just need to update your SDK and imports.
121128

122-
1. Update your SDK:
129+
1. Install the new SDK
123130

124131
```
125132
pip install agentstack-sdk
126133
```
127134

128-
2. Update your imports:
135+
2. Update your imports
129136

130137
```
131138
from agentstack_sdk import Server
132139
```
133140

134-
3. Rebuild your container images.
141+
3. Rebuild your container images to apply naming and dependency changes - no code logic changes are required
142+
143+
### If You Host Your Own Stack (via Helm)
144+
145+
If you’re running your own instance using Helm, this release requires a clean reinstall. Simply uninstalling isn’t
146+
enough because Helm leaves persistent volumes behind. A full reinstall avoids configuration conflicts and ensures
147+
compatibility with the new version.
148+
149+
**Note:** Old conversations, agent data, and configurations won’t carry over. Start fresh for a clean environment.
135150

136151
## What’s Next
137152

0 commit comments

Comments
 (0)