Files
dirigent/README.md
T
2026-05-09 19:52:44 +02:00

79 lines
3.2 KiB
Markdown

# Dirigent
<p align="center">
<img src="dirigent.svg" alt="Dirigent" width="64" height="64">
</p>
<p align="center">Core libraries for the Dirigent agent orchestration platform.</p>
> **Alpha software.** Dirigent is in early active development and not fully battle-tested. Most crates are experimental — APIs will change without notice. There is nothing to install from this repository yet. The standalone tools listed below have their own repositories and maturity levels.
---
## Standalone Tools
These tools are developed in this monorepo but distributed as independent repositories. Install them from their own repos:
| Tool | Repository | Maturity | Description |
|------|-----------|----------|-------------|
| **fermata** | [git.g4b.org/dirigence/fermata](https://git.g4b.org/dirigence/fermata) | production (core), beta (toml config) | Policy gate for AI coding agents — `.botignore` enforcement |
| **anth** | [git.g4b.org/dirigence/dirigent_anth](https://git.g4b.org/dirigence/dirigent_anth) | production (library), beta (CLIs) | Tools for working with Claude Code session data |
| **dirigate** | [git.g4b.org/dirigence/dirigate](https://git.g4b.org/dirigence/dirigate) | beta (bridge/mock), concept (connect/ingest) | ACP bridge connecting stdio agents to Dirigent |
---
## Architecture
<p align="center">
<img src="architecture.svg" alt="Dirigent package architecture" width="720">
</p>
**Layers top-to-bottom:**
- **Consumers** *(shadow)* — server assembly, web app, integrations — not in this repo
- **Standalone Tools** — installable from their own repositories; depend on these crates
- **Orchestration** — connector runtime, ACP server, introspection
- **Foundation** — protocol types, tool sandbox, configuration, auth, process management
---
## Crates
| Crate | Maturity | Description |
|-------|----------|-------------|
| `dirigent_core` | beta | Multi-connector orchestration runtime |
| `dirigent_protocol` | beta | ACP protocol types — messages, events, and RPC definitions |
| `dirigent_acp_api` | beta | ACP server for incoming agent connections |
| `dirigent_inspector` | concept | Runtime introspection tree |
| `dirigent_config` | beta | Configuration management |
| `dirigent_auth` | concept | User authorization model |
| `dirigent_process` | beta | Child process management |
| `dirigent_tools` | concept | Tool sandbox and execution abstractions |
| `opencode_client` | beta | OpenCode.ai HTTP client |
---
## Library Usage
Add a crate to your `Cargo.toml`:
```toml
[dependencies]
dirigent_protocol = { git = "https://git.g4b.org/dirigence/dirigent", path = "crates/dirigent_protocol" }
dirigent_core = { git = "https://git.g4b.org/dirigence/dirigent", path = "crates/dirigent_core" }
```
Replace the crate name and path with the one you need. All crates follow the same pattern.
> **Expect breakage.** These are internal library crates under active development. Pin to a specific commit if you depend on stability.
---
## License
Licensed under either of
- Apache License, Version 2.0 ([LICENSE-APACHE](LICENSE-APACHE) or <https://www.apache.org/licenses/LICENSE-2.0>)
- MIT License ([LICENSE-MIT](LICENSE-MIT) or <https://opensource.org/licenses/MIT>)
at your option.