Project docs
YodaMan Docs
Quick, browser-friendly summaries with links back to the source Markdown files in the repository.
Ecosystem Architecture
YodaMan is organized around one shared local runtime used by the web UI, desktop app, VS Code extension, mobile companion, CLI, and mandatory Graphify knowledge graph layer.
- Runtime owns agent execution, tools, indexing, sessions, plugins, audit, and safety policy.
- Graphify runs with Ollama local execution only for graph-aware answers, impact analysis, and architecture maps.
- Clients own UX: editor actions, desktop control, mobile approvals, and notifications.
- REST and SSE provide the current protocol.
Security And Audit
The runtime includes baseline hardening for local agent tools.
- Workspace-scoped file and command paths.
- Blocked high-risk shell command patterns.
- Audit log entries for tool calls.
- Optional pairing-token enforcement for non-local clients.
Mobile Linking
The phone must connect to the Mac's LAN address, not 127.0.0.1.
curl -X POST http://127.0.0.1:3090/api/pairing \
-H "Content-Type: application/json" \
-d '{"runtimeUrl":"http://YOUR-MAC-LAN-IP:3090"}'
Paste the returned yodaman://pair deep link into the mobile app and tap Use Pairing Link.
Downloads and Updates
YodaMan gives you a choice of clients so you can work from the environment that fits the moment.
- Desktop downloads are available for macOS, Windows, and Linux.
- The VS Code extension is available on the Visual Studio Marketplace.
- Mobile companion clients help you monitor tasks and approve changes while away from your desktop.
- Release notes highlight meaningful product changes so you can update with confidence.
API Reference
Important runtime endpoints include:
POST /api/agent/taskGET /api/agent/tasksGET /api/agent/tasks/:taskId/eventsGET /api/agent/pending-approvalsGET /api/policyGET /api/auditPOST /api/pairingGET /api/graphify/statusPOST /api/graphify/affectedGET /api/graphify/map
Choosing A Client
Use the desktop app when you want the full control center, the VS Code extension when you are actively coding, and mobile when you only need oversight away from the keyboard.
- Desktop: manage projects, plugins, indexing, sessions, model settings, runtime health, and approvals.
- VS Code: ask workspace questions, run coding tasks, review diffs, and keep streamed tool events beside your editor.
- Mobile: monitor tasks, search projects, receive notifications, and approve or reject pending changes.