Use today
One service, on your machine
For coordinating several agents and people. MCP, HTTP, a command line, a board, a graph and a history; quiet claims and automatic backups. Version 0.1.0: no TLS, no access by team.
Planning and coordination for people and AI agents
When agents do real work beside people, the plan is what they all share. Vigile holds it as one graph of outcomes, dependencies, responsibility, state and history, changed only through checked operations: true enough to act on, and open for an agent to inspect and improve.
Use today
For coordinating several agents and people. MCP, HTTP, a command line, a board, a graph and a history; quiet claims and automatic backups. Version 0.1.0: no TLS, no access by team.
Direction · not built, no dates
The same graph and operations could carry one plan across teams and tools: access by team, a hosted service, an observer of plan health. None of it is built.




Today · why not a list of issues, or a file of notes
what can start now
Say what depends on what and set priorities on areas and tasks. Vigile follows the active path from outermost group to task, holds work back for unfinished dependencies or inactive containers, and answers "what can I do next?" each time it is asked.
refusals
Starting a task whose dependency is unfinished, closing a group over open work, a jump of status the rules do not allow: each is refused, and the refusal says why, and what would resolve it, for a person to read or an agent to follow.
$ vigile set-task-status --id WEB-003 --version 1 \
--status in_progress --as agent1
✗ Task WEB-003 cannot be started: it is waiting for a
dependency to finish.
· WEB-002 Cart page lists the items and the total open
→ Finish or cancel the items it depends on.
→ Or call remove_link with type "depends on" if the
dependency no longer applies.
→ Or call list_next_tasks to pick work that can start now.
versions
Changing a task names the version the change was based on. Of two agents that start the same task, one is refused. Assigned work quiet for 24 hours can be listed for attention, but is never silently taken away.
And it keeps the plan in sight
The whole plan in one picture, grouped into areas, with its dependencies, its work in progress and its priorities, also shows how the work is cut: tasks that belong to no group, a group grown too wide, too many unrelated things started at once. An agent can read the same plan through the same lists.
A task that contains tasks is a group, and reports how far along it is. Groups
Reopen a dependency after the work that needed it went on, and the task and its project say so. Problems
A task and a project keep what was done to them and each status they went through. History
Zoom the board into a project or through nested groups, filter it, read who changed what across the plan, inspect an item and adjust task priority. Every view, selection, item and zoom has an address. The web page




One plan, four ways in
Each of the 21 operations is defined once and offered as an MCP tool for agents, an HTTP endpoint for programs and a command for you. The page reads through the same operations, so a change made one way shows for all.
Try it in two minutes
It needs Node.js 22.13 or later and pnpm. No database server and no account. It listens on 127.0.0.1, sends nothing anywhere, and takes a backup every 24 hours by default.
Get it and build it.
git clone https://github.com/dluc/vigile.git ~/code/vigile
cd ~/code/vigile
pnpm install
pnpm buildCreate an instance and start it.
cd ~/code/vigile
bin/vigile config init --config ~/vigile/main/config.toml --name main
bin/vigile serve --config ~/vigile/main/config.tomlOpen the board, and point an agent at the plan. serve prints where everything is:
MCP http://127.0.0.1:8700/mcp
Web http://127.0.0.1:8700/
API http://127.0.0.1:8700/apiToday · said plainly
Vigile is new: version 0.1.0, developed and tested on Linux, under the MIT licence. Where it could go, and why that is credible, is on the vision, marked as direction.