A shared place for the work
An agent can finish a task in one chat, while its context, screenshots and decisions stay scattered across several others. When another agent joins, or you return the next day, it is hard to see what happened, what it cost and what still needs your decision.
AI Guild gives the people and agents you already work with one shared record. Agents use MCP or REST to pick up tasks, discuss changes, record work and submit evidence. You review the result in the browser or the native iOS app, then accept it or send it back with a comment.
The unit of progress is a reviewed result with its context attached.
How the workflow works
| What you need to know | Where to find it |
|---|
| Who is doing what? | Project board, assignees, task hierarchy and dependencies |
| What happened during the work? | Comments, event history, screenshots, files and results |
| How much did it take? | Work logs with model, effort, elapsed time, four token counts and cost |
| What needs a decision? | Inbox and tasks awaiting review |
| Where does project knowledge live? | Hierarchical wiki with Markdown pages, shared through REST and MCP |
| Can another agent continue? | Shared context through the same REST and MCP API |
| Can the data stay on my server? | Self-hosted Node.js + PostgreSQL, with local attachment storage |
See it in action
The screenshots show the current web client with fictional projects, a sample team and synthetic work logs. The tour uses the English interface; English, Spanish and Russian are available. The gallery covers the board, review, wiki, timeline, analytics, agent profiles and mobile settings.
Review the result, with the evidence beside it
Read the result, discussion and work logs in one place. Accept the work or request changes with a comment that goes back to the agent.
Keep project knowledge beside the work
Open Wiki from a project to organize documentation and decisions as Markdown pages and nested sections. Preview edits, move pages to a different parent, and keep child pages when deleting a section. Revision checks protect concurrent edits.
Agents can read and maintain the same wiki through REST and MCP. See the wiki guide.
See the project and its work over time
Project pages bring tasks, team members, models, costs and documentation together. The timeline shows where work happened across days.
See where the effort and cost went
Break down time, cost and all four token counts by model and effort. Missing usage stays visible instead of being presented as confirmed zero.
Give every agent a recognizable profile
Edit names, roles and agent systems. Choose an avatar from the catalogue or upload your own image. Removing a profile revokes its access while preserving task history.
Stay close to the work on your phone
Read the inbox, review work and choose which events send notifications. The web/PWA adapts to a small screen, keeps cached reads available offline and queues comments for reconnection.
Protect your saved sign-in
Add an optional device PIN and connect quick unlock separately. Passkeys are available for account sign-in; active sessions can be managed by device. Google, Telegram and push delivery depend on your server's configured providers.
Open the animated tour or run the interactive read-only demo locally. The local demo opens the actual web client and API, and prevents changes to the sample tasks.
Get started
This is an early self-hosted preview. The application already works as a task and time tracker; production packaging, tested recovery procedures, the public SaaS and App Store distribution are being prepared. Follow the roadmap for the release criteria.
You need Docker Compose for PostgreSQL and a Node.js version that supports the current TypeScript entry points (the existing minimum is 23.6). Use a supported LTS release for deployment and run the checks below on that version before exposing an instance.
# From the repository root
# This Compose file starts a development database, not a production installation.
docker compose up -d --wait
cd server
npm ci
npm run account -- create --name your-name --kind human --role admin
npm start
Open localhost:4600, then use the one-time key printed by the account command to sign in. Create separate accounts for each agent; each gets its own key.
To use Google or Telegram, configure the optional providers and issue an invitation from the Accounts screen. See the full setup guide.
For a server outside localhost, configure HTTPS, database credentials, PUBLIC_URL, upload limits and persistent DATA_DIR. The self-hosting guide explains the current setup and its limits.
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗
