Open-source Team Context Engine for human and AI teams
590
Devsync is an open-source, self-hosted Team Context Engine that keeps human teams, assistants, automations, and AI agents aligned through a local-first, Git-versioned project memory.
It turns scattered updates, decisions, resources, tasks, work files, and AI instructions into shared operational context stored in readable Markdown and JSON files.
docker run -p 4000:4000 \
-v devsync-data:/data \
-e AUTH_MODE=none \
caporro/devsync:latest
Open:
http://127.0.0.1:4000
AUTH_MODE=none is only for private local use. For deployment, use password auth.
AI makes teams faster, but faster output creates a new bottleneck: keeping everyone aligned on the real state of the work.
Devsync gives each project a durable context layer where:
Generate a password hash:
node scripts/hash-password.mjs
Run:
docker run -d \
--name devsync \
-p 4000:4000 \
-v devsync-data:/data \
-e AUTH_MODE=password \
-e '[email protected]|Name|scrypt$...' \
-e AUTH_SESSION_SECRET='change-me-to-a-long-random-string-at-least-32-chars' \
-e AUTH_COOKIE_SECURE=true \
-e OPENAI_API_KEY='sk-...' \
caporro/devsync:0.1.25
Notes:
/data;AUTH_COOKIE_SECURE=true only behind HTTPS;AUTH_MODE=none on shared servers.data/<vault>/
README.md
assistant.md
vault-plan.json
config/
skills.json
skills/
automations/
docs/
projects/
project-id/
project.json
README.md
assistant.md
automations/
resources/
tasks/
logs/
work/
Meaning:
resources/: source material, uploads, links, notes, images, PDFs, Excalidraw files;tasks/: task files, owners, deadlines, and task index;logs/activity/: append-only project activity log;work/: output produced or refined by people, Assistant, or automations;assistant.md: AI instructions;automations/: automation definitions;skills/: reusable Assistant skills;vault-plan.json: global planning data.The vault can be inspected directly and versioned with Git.
Devsync includes:
/mcp;MCP tools include:
list_projects;get_project;search_files;read_file;list_tasks;read_task;create_task;update_task;toggle_task;delete_task.Your team context stays in files your team owns.
Markdown and JSON are readable by humans, agents, editors, shell tools, and Git. The data remains usable outside the Devsync UI, while the app adds structure, Assistant, automations, MCP, activity logs, tasks, and operational workflows.
No database does not mean no structure. It means the structure lives in files.
Full configuration reference:
https://github.com/caporro/devsync/blob/main/docs/reference/env-vars.md
Main variables:
PORT=4000
HOST=0.0.0.0
DEVSYNC_VAULT_NAME=devsync-vault
DEVSYNC_DATA_ROOT=/data
AUTH_MODE=password
[email protected]|Name|scrypt$...
AUTH_SESSION_SECRET=change-me-to-a-long-random-string-at-least-32-chars
AUTH_COOKIE_SECURE=true
DEVSYNC_AGENT_MODEL=openai:gpt-4.1-mini
OPENAI_API_KEY=sk-...
MIT.
Content type
Image
Digest
sha256:57dbcd6c7…
Size
91 MB
Last updated
4 months ago
docker pull caporro/devsync