bamboo-server 2026.7.12

HTTP server and API layer for the Bamboo agent framework
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

//! Server-only tools and tool executors.
//!
//! These tools are registered only when running the Bamboo HTTP server.
//! They may depend on `AppState` components (storage, schedulers, etc.).
//!
//! Framework-agnostic tools (MemoryTool, OverlayToolExecutor, SubAgentTool,
//! etc.) live in the `bamboo-server-tools` crate. This module re-exports them
//! for convenience and keeps the server-bound glue (`ChildSessionAdapter`,
//! `ScheduleTasksTool`) that wires those tools to `AppState` via ports.

// Re-export framework-agnostic tools from the bamboo-server-tools crate.
pub use bamboo_server_tools::{
    AskAgentTool, ClusterTool, CompactContextTool, DeployAgentTool, DeployedRegistry,
    LoadSkillTool, MemoryTool, NotificationDispatcher, NotifyTool, OverlayToolExecutor,
    ReadSkillResourceTool, SessionInspectorTool, SubAgentTool, ToolSurface, ToolSurfaceFactory,
};

pub mod child_session_adapter;
pub mod model_catalog;
pub mod notify_dispatcher;

// Integration tests that wire `SubAgentTool` to a real `ChildSessionAdapter`
// (the tool itself + its pure unit tests live in `bamboo-server-tools`).
#[cfg(test)]
mod sub_agent_tests;

pub type SubagentModelResolver = std::sync::Arc<
    dyn Fn(String) -> futures::future::BoxFuture<'static, Option<bamboo_domain::ProviderModelRef>>
        + Send
        + Sync,
>;
pub type OptionalSubagentModelResolver = Option<SubagentModelResolver>;

// Re-export server-specific tool types for convenience
pub use child_session_adapter::ChildSessionAdapter;
pub use model_catalog::RegistryModelCatalog;
pub use notify_dispatcher::ServerNotificationDispatcher;