docs: Document Agent.clone_for_channel() method and multi-channel gateway isolation#458
Conversation
… gateway isolation (fixes #448) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Mervin Praison <MervinPraison@users.noreply.github.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
Warning Review limit reached
More reviews will be available in 40 minutes and 38 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Code Review
This pull request introduces documentation for the new "Agent Cloning" feature, which allows safely cloning agents for multi-channel, multi-tenant, or per-session isolation, resolving previous RLock pickling errors. The documentation updates span several files, including bot-gateway, channels-gateway, messaging-bots, and thread-safety. The review feedback highlights several instances where internal links should be updated to use the full /docs/features/... path instead of /features/... to ensure consistency and prevent unnecessary redirects.
| <Card title="Bot Gateway" icon="server" href="/features/bot-gateway"> | ||
| Multi-channel gateway using agent cloning | ||
| </Card> | ||
| <Card title="Thread Safety" icon="shield" href="/features/thread-safety"> | ||
| Agent thread safety and concurrency | ||
| </Card> |
There was a problem hiding this comment.
To maintain consistency with the rest of the documentation and avoid unnecessary redirects, internal links should use the full /docs/features/... path instead of /features/....
<Card title="Bot Gateway" icon="server" href="/docs/features/bot-gateway">
Multi-channel gateway using agent cloning
</Card>
<Card title="Thread Safety" icon="shield" href="/docs/features/thread-safety">
Agent thread safety and concurrency
</Card>
| style Clone1,Clone2,Clone3 fill:#10B981,color:#fff | ||
| ``` | ||
|
|
||
| Each clone has fresh locks and interrupt controllers, preventing cross-channel interference. Learn more about [Agent Cloning](/features/agent-cloning). |
There was a problem hiding this comment.
| This starts Pattern B host integration with channels feature enabled. | ||
|
|
||
| <Note> | ||
| All configured channels now start reliably from a single gateway, resolving the previous `cannot pickle '_thread.RLock' object` error through automatic [Agent Cloning](/features/agent-cloning). |
There was a problem hiding this comment.
Update the internal link to use the full /docs/features/... path to ensure consistency and prevent redirects.
All configured channels now start reliably from a single gateway, resolving the previous `cannot pickle '_thread.RLock' object` error through automatic [Agent Cloning](/docs/features/agent-cloning).
| ``` | ||
|
|
||
| <Tip> | ||
| Behind the scenes the gateway calls `Agent.clone_for_channel()` on the configured agent for each channel, so per-channel tools or routing rules never leak between bots. See [Agent Cloning](/features/agent-cloning). |
There was a problem hiding this comment.
Update the internal link to use the full /docs/features/... path to ensure consistency and prevent redirects.
Behind the scenes the gateway calls `Agent.clone_for_channel()` on the configured agent for each channel, so per-channel tools or routing rules never leak between bots. See [Agent Cloning](/docs/features/agent-cloning).
| <Card title="Agent Cloning" icon="copy" href="/features/agent-cloning"> | ||
| Clone agents for channel isolation | ||
| </Card> |
Fixes #448
Summary
Documentation Changes
The new documentation covers:
Validation
🤖 Generated with Claude Code