bazel start + mcp start
This commit is contained in:
1 parent
a90653260a
commit
4c082aca7c
33 files changed
+1728
-79
No files matched your search
@@ -8,7 +8,7 @@ With `channels:history` and the other read scopes, a container holding the bot t
|
||||
|
||||
## Shape
|
||||
|
||||
- The bot exposes the tools through the same in-container MCP server as `send_file` ([send-files-to-user.md](send-files-to-user.md)). The container side stays a thin relay: it forwards each call to the bot, and the bot answers.
|
||||
- The bot exposes the tools through the same in-container MCP server as `send_file` (`internal/tools`). The container side stays a thin relay: it forwards each call to the bot, and the bot answers.
|
||||
- **Getting calls to the bot:** the relay talks back over the agent connection the bot already has open (a new ACP extension method such as `_slackerbot/call`, which goose would pass through from the MCP server, if it can), or over a new stream from container → node → master. The second option is a new direction on the cluster link (slave → master) and has to be additive, because masters and slaves may run different versions for a while.
|
||||
- **Every call is scoped to the session's owner:** the channel (or the user's DM) and its threads. The bot checks this, not the container.
|
||||
|
||||
|
||||
Reference in new issue
Block a user