Expand description
Configuration management for devboy-tools.
Handles loading and saving configuration from TOML files. Config files are stored in platform-specific locations:
- macOS/Linux:
~/.config/devboy-tools/config.toml - Windows:
%APPDATA%\devboy-tools\config.toml
§Example
ⓘ
use devboy_core::config::{Config, GitHubConfig};
// Load config
let config = Config::load()?;
// Modify config
let mut config = config;
config.github = Some(GitHubConfig {
owner: "meteora-pro".to_string(),
repo: "devboy-tools".to_string(),
});
// Save config
config.save()?;Structs§
- Builtin
Tools Config - Configuration for controlling which built-in tools are available.
- Click
UpConfig - Config
- Main configuration structure.
- Confluence
Config - Context
Config - Per-context provider configuration.
- Fireflies
Config - Fireflies.ai provider configuration (meeting notes).
- Format
Pipeline Config - Configuration for the format pipeline (TOON encoding, budget trimming, strategies).
- GitHub
Config - GitLab
Config - Jira
Config - Proxy
Config - Container for global proxy configuration — wired under
[proxy]in TOML. - Proxy
Matching Config - Proxy
McpServer Config - Configuration for an upstream MCP server to proxy.
- Proxy
Routing Config - Routing policy: global default strategy plus per-tool overrides.
- Proxy
Routing Override - Per-server partial override for
ProxyRoutingConfig. - Proxy
Secrets Config - Secure-store configuration for proxy authentication tokens.
- Proxy
Telemetry Config - Telemetry pipeline configuration — reports routing decisions to a configurable HTTP endpoint even when the call is executed locally.
- Proxy
Tool Rule - Per-tool override: maps a tool-name glob pattern to a specific routing strategy.
Patterns are matched against the tool name without the upstream prefix
(e.g.,
get_issues, notcloud__get_issues). - Remote
Config Settings - Remote configuration endpoint settings.
- Sentry
Config - Sentry error reporting configuration.
- Slack
Config - Slack provider configuration (messenger).
Enums§
- Routing
Strategy - Routing strategy — how a tool invocation is dispatched when both the local executor and a connected upstream MCP server can handle the same tool.
Functions§
- default_
slack_ required_ scopes - matches_
glob - Match
nameagainst a glob-likepatternwhere*is a wildcard matching any run of characters (including empty). No character classes, escapes, or?. - routing_
strategy_ slug - Stable kebab-case slug for a
RoutingStrategy. Symmetric with serde and TOML serialisation. Exported so CLI / observability code renders strategy values the same way in every surface (JSON, plain text,config list).