You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,8 @@ Check if `@AGENTS_STEWARD.md` exists. If yes, follow the instructions there. If
8
8
9
9
**Save what you produce:** after coding tasks touching `/lib/`, propose or update the module spec (`specs_propose` purpose/invariants/workflows); after a repeatable procedure, save a skill (`skill_save`); after working out a plan with the user, save it as a document under `documents/plans/<slug>`; run `query_specs(undocumented: true)` to find modules missing specs. See the `steward_get_started` guidance packet for the store decision.
10
10
11
+
**Keep the public docs current:**`/docs` is compiled from `README.md`, `guides/`, and `priv/skills/steward-installer.md`. Any change to installation, behavior, configuration, deployment, or testing must update the matching source document in the same task.
12
+
11
13
## Guides
12
14
13
15
Project-specific workflows live in `guides/`. Check them before starting work:
**Documentation: [stewardacs.xyz/docs](https://stewardacs.xyz/docs)** — installation, configuration, development, deployment, and testing guides published from this repository.
8
+
9
+
New to Steward? Start with [what Steward is, how to connect agents, and how teams use it](guides/getting-started.md).
10
+
7
11
Steward ACS is an **infrastructure layer** for multi-agent coordination. It runs as a standalone Phoenix web application (port 4001) and exposes MCP (Model Context Protocol) tools that any AI agent — Claude, GPT, Llama, or any MCP-compatible client — can call directly. It does not do the work itself; it manages the agents who do.
# Steward: a shared operating system for AI agents
2
+
3
+
Steward helps people coordinate AI agents that work on the same projects.
4
+
5
+
Without coordination, two agents can edit the same file, repeat the same investigation, or make decisions without telling the rest of the team. Steward gives them one shared place to declare work, avoid collisions, and preserve what they learn.
6
+
7
+
Steward does **not** replace your coding agent, chat assistant, repository, or project tracker. It connects to agents through MCP and adds a coordination layer around the tools you already use.
8
+
9
+
## What Steward does
10
+
11
+
| Need | Steward capability | Result |
12
+
|---|---|---|
13
+
| Know who is doing what | Tasks and agent presence | People and agents can see active work before starting something new. |
14
+
| Prevent conflicting edits | File locks | Agents avoid changing the same file at the same time. |
15
+
| Stop rediscovering decisions | Memories | Durable decisions, warnings, and patterns follow the team. |
16
+
| Keep code intent understandable | Specs | Agents see a module's purpose and invariants before changing it. |
17
+
| Reuse proven procedures | Skills | Installation, deployment, debugging, and support workflows become repeatable. |
18
+
| Keep long-form knowledge available | Documents | Plans, policies, briefs, and reference material remain searchable. |
19
+
20
+
## Who it is for
21
+
22
+
- A developer using more than one coding agent or editor.
23
+
- A team whose agents work across the same repositories.
24
+
- An organization that wants agent decisions and procedures to survive beyond one chat session.
25
+
- Operators who need to see active work, review shared knowledge, and control access by organization and role.
26
+
27
+
For one short, isolated agent task, Steward may be unnecessary. It becomes useful when work overlaps, repeats, or needs to be handed between people and agents.
28
+
29
+
## Set up Steward
30
+
31
+
Choose one of these paths:
32
+
33
+
1.**Use a hosted organization:** create or join an organization from the Steward sign-in page. Your organization gets an isolated workspace and MCP endpoint.
34
+
2.**Run Steward yourself:** follow the [installation guide](/docs/install). The default local setup uses Docker, SQLite, and no LLM provider.
35
+
36
+
After setup, open the Steward dashboard. It shows the MCP endpoint and copy-ready instructions for connecting chat and coding agents.
37
+
38
+
## Connect a coding agent
39
+
40
+
The exact settings screen differs by agent, but the flow is the same:
41
+
42
+
1. In the Steward dashboard, copy the **coding MCP endpoint** and coding-agent instructions.
43
+
2. Add the endpoint as an MCP server in Codex, Cursor, Claude Code, OpenCode, or another MCP-compatible client.
44
+
3. Complete the browser sign-in when using a hosted organization. A local installation uses its configured API key instead.
45
+
4. Paste the coding-agent instructions into the repository's `AGENTS.md` or equivalent rules file.
46
+
5. Restart or reconnect the agent so it discovers the Steward tools.
47
+
6. Ask the agent to check Steward. A successful connection returns its identity, repository context, and current work guidance.
48
+
49
+
Example remote configuration:
50
+
51
+
```toml
52
+
[mcp_servers.steward]
53
+
url = "https://YOUR-STEWARD-HOST/mcp/sse"
54
+
```
55
+
56
+
Keep the generated repository instructions in version control when they contain no secrets. Keep API keys and local environment files out of version control.
57
+
58
+
## Connect a chat agent
59
+
60
+
Use the dashboard's **chat MCP endpoint** and chat instructions when connecting a conversational assistant such as Claude or ChatGPT.
61
+
62
+
Chat agents get a smaller, safer tool surface for finding knowledge, reading skills and documents, checking work status, and saving approved information. Coding agents additionally receive task and file-locking tools because they modify repositories.
63
+
64
+
## The normal agent workflow
65
+
66
+
Once connected, agents should follow this loop:
67
+
68
+
1.**Check context:** identify the repository and load relevant memories, specs, and skills.
69
+
2.**Claim work:** create or claim a task before making changes.
70
+
3.**Lock files:** reserve the files that will be edited.
71
+
4.**Do and verify the work:** change the project and run the smallest meaningful checks.
72
+
5.**Save reusable knowledge:** update a spec, skill, document, or memory when the work produced something future agents need.
73
+
6.**Release and report:** release the task and submit feedback so the next person or agent sees a clean state.
74
+
75
+
The human remains responsible for priorities, approvals, and decisions that change scope. Steward makes the agent's work visible; it does not grant agents authority they did not already have.
76
+
77
+
## How this helps a team
78
+
79
+
### Fewer collisions
80
+
81
+
Before editing, an agent can see that another agent already owns a task or file. The team spends less time resolving duplicate work and conflicting patches.
82
+
83
+
### Better handoffs
84
+
85
+
A task records the current unit of work. Specs explain why code exists. Memories preserve decisions and warnings. A different person or agent can continue without reconstructing the full history from chat transcripts.
86
+
87
+
### Consistent procedures
88
+
89
+
When a deployment, installation, or support workflow works, save it as a skill. Future agents retrieve the same verified steps instead of improvising a new procedure.
90
+
91
+
### Shared knowledge with boundaries
92
+
93
+
Organizations, teams, projects, roles, and authority levels control who can see or change shared information. Local ACS instances remain test-only; team knowledge belongs in the shared Steward organization.
94
+
95
+
### Human oversight
96
+
97
+
The dashboard shows active agents, tasks, memories, documents, skills, tool requests, and errors. Humans can review the operating context instead of relying on each agent to summarize itself accurately.
98
+
99
+
## A practical team rollout
100
+
101
+
1. Start with one repository and two or three people.
102
+
2. Add the Steward MCP connection and repository instructions to every agent used on that repository.
103
+
3. Require task claiming and file locking for all code changes.
104
+
4. Save only durable knowledge: decisions, invariants, warnings, and repeatable procedures.
105
+
5. Review memories, specs, and skills regularly; archive or correct anything stale.
106
+
6. Expand to more repositories after the workflow feels routine.
107
+
108
+
The goal is not to store every conversation. The goal is to keep the small amount of context that prevents the team from repeating mistakes.
109
+
110
+
## Next steps
111
+
112
+
-[Install Steward](/docs/install)
113
+
-[Review configuration and secrets](/docs/configuration)
114
+
-[Understand remote versus local development](/docs/development)
0 commit comments