Building Integrations
Patterns for connecting Codebolt to external services and platforms. Each pattern covers: which mechanism to use, how it's wired, and a minimal working example.
This is distinct from Extending Codebolt (adding features inside the Codebolt app) and from Plugins (the SDK reference). This section is about what to build when you need Codebolt to talk to the outside world.
Integration patterns
| Pattern | Mechanism | Section |
|---|---|---|
| Chat platform (Telegram, Discord, Slack) | Custom client via clientsdk | Chat Integrations |
| CI/CD (GitHub Actions, GitLab CI, Jenkins) | Hooks + plugin bus, or headless clientsdk | CI/CD Integration |
| Project management (Linear, Jira, GitHub Issues) | Webhooks + plugin | Project Tool Integration |
| IDE / editor (VS Code, Neovim, JetBrains) | Custom client via clientsdk | IDE Integration |
| Custom API gateway | Plugin gateway hook | API Gateway |
Picking the right mechanism
Does your integration drive agent runs from outside Codebolt?
→ Custom client (clientsdk). You own the interface; the server handles the run.
Does your integration react to agent events or intercept them?
→ Plugin hook. Lightweight, event-driven, stays inside the server's lifecycle.
Does your integration expose Codebolt over a new protocol or platform?
→ Custom client + gateway plugin. The client translates the platform protocol;
the plugin handles auth and routing inside the server.
See also
- Custom UIs — clientsdk reference
- Plugins — hook and plugin bus reference
- Extending Codebolt — adding features inside the app