-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathindex.astro
More file actions
138 lines (124 loc) · 5.71 KB
/
index.astro
File metadata and controls
138 lines (124 loc) · 5.71 KB
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
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
---
import DocsLayout from '../../layouts/DocsLayout.astro';
---
<DocsLayout title="Documentation | AgentCrew" lang="en">
<div class="docs-prose">
<h1>Documentation</h1>
<p>
AgentCrew is an open-source AI agent orchestrator. Just as Kubernetes
orchestrates containers regardless of what application runs inside,
AgentCrew orchestrates AI agents regardless of their purpose.
</p>
<p>
Create teams of specialized agents for any domain: software engineering,
marketing, finance, data analysis, content creation, operations, or
anything else. Agent specialization is driven entirely by documentation:
write Markdown instructions describing what each agent should do, and
AgentCrew handles deployment, communication, and coordination.
</p>
<p>
Supports multiple AI providers including Claude Code and OpenCode.
Choose the provider that best fits your needs when creating a team.
</p>
<h2>Key Concepts</h2>
<h3>Teams</h3>
<p>
A team is a group of AI agents that work together on a shared mission.
Each team runs in its own isolated environment (Docker containers with a
dedicated NATS messaging bus). You can have multiple teams running
simultaneously, each focused on a different project or domain.
</p>
<h3>Agents: Leader + Workers</h3>
<p>
Every team has exactly one <strong>leader</strong> and one or more
<strong>workers</strong>. The leader receives your messages, breaks down
the work, and delegates to workers. Workers are specialist agents defined
by Markdown files. Their role, instructions, and behavior are entirely
determined by the documentation you write. A worker can be anything: a
"Content Strategist", a "Financial Analyst", a "Backend Developer", or a
"Legal Reviewer". The same orchestration platform, infinite use cases.
</p>
<h3>Documentation-Driven Specialization</h3>
<p>
The core of AgentCrew is that agents are defined by text. The system
generates structured files that determine each agent's behavior:
</p>
<ul>
<li><strong>CLAUDE.md</strong>: The leader's instructions, team context, and delegation protocol.</li>
<li><strong>agents/*.md</strong>: One file per worker, with YAML frontmatter (name, model, skills) and a Markdown body containing detailed instructions.</li>
<li><strong>Skills</strong>: Installable extensions from GitHub repos that give agents additional capabilities.</li>
</ul>
<p>
This documentation-driven approach means you can create agents for any
purpose without writing a single line of code. Describe what the agent
should do, and it becomes that specialist.
</p>
<h3>Skills</h3>
<p>
Skills are extensions that give agents specialized capabilities sourced
from GitHub repositories. Skills can be installed on individual workers
(agent-specific) or on the leader (global, shared with all agents in the
team). They allow you to extend what your agents can do without modifying
their core instructions.
</p>
<h3>Workspaces</h3>
<p>
A workspace is a directory mounted into the agent container at
<code>/workspace</code>. It gives agents access to your project files,
including source code, documents, data, and configuration, so they can read, edit, and
create files on your behalf. Workspaces persist across sessions.
</p>
<h2>Documentation Sections</h2>
<ul>
<li>
<a href="/docs/quick-start"><strong>Quick Start</strong></a>:
Get AgentCrew running in one command with Docker Compose.
</li>
<li>
<a href="/docs/configuration"><strong>Configuration</strong></a>:
Environment variables, application settings, and storage options.
</li>
<li>
<a href="/docs/providers"><strong>Providers</strong></a>:
Supported AI providers (Claude Code, OpenCode) and how to configure each.
</li>
<li>
<a href="/docs/open-source-models"><strong>Open Source Models</strong></a>:
Run agents locally with Ollama — no API keys needed, full data privacy.
</li>
<li>
<a href="/docs/skills"><strong>Skills</strong></a>:
How to extend agent capabilities with installable skills.
</li>
<li>
<a href="/docs/schedules"><strong>Schedules</strong></a>:
Automate recurring tasks with cron-based schedules and track run history.
</li>
<li>
<a href="/docs/webhooks"><strong>Webhooks</strong></a>:
Trigger agent teams from external systems via HTTP with token-authenticated endpoints and prompt templates.
</li>
<li>
<a href="/docs/post-actions"><strong>Post-Actions</strong></a>:
Reusable HTTP callbacks that fire automatically after webhook or schedule runs to notify external systems.
</li>
<li>
<a href="/docs/mcp"><strong>MCP Servers</strong></a>:
Connect agents to external tools (databases, APIs, Kubernetes) via the Model Context Protocol.
</li>
<li>
<a href="/docs/authentication"><strong>Authentication</strong></a>:
Built-in user authentication, organizations, invites, and role-based access control.
</li>
<li>
<a href="/docs/architecture"><strong>Architecture</strong></a>:
System components, messaging, container internals, and runtime design.
</li>
</ul>
<h2>License</h2>
<p>
AgentCrew is open source software licensed under the
<a href="https://github.com/helmcode/agent_crew/blob/main/LICENSE" target="_blank" rel="noopener noreferrer">GNU Affero General Public License v3.0 (AGPL-3.0)</a>.
</p>
</div>
</DocsLayout>