Waz's Agent capabilities will be implemented in the form of independent open source services and will not be bound to the Warp client. The terminal is just one of its carriers - TUI, IDE plug-ins, and cloud workers can all drive the same engine.
- Independently design and implement an open source Agent service from scratch - covering Agent loop, tool runtime, session/history state, prompt word template, provider routing; does not bind Warp's existing client code. Waz as its first official carrier.- Define stable IPC / JSON-RPC protocol: prompt words, streaming token, tool call, file diff, status, attachment.- Harness is released as a reusable open source service that can be accessed by headless daemons, independent TUIs, IDE plug-ins, and other terminals.- The default is to run purely locally; credentials, history, skills, and MCP server configuration are all retained locally.- The protocol comes with version number and capability negotiation, and the client and Harness can be upgraded independently.- The tool registry is pluggable: built-in shell / read / edit / search and other tools, and allows users to provide external tools through a unified RPC interface.
- The same Harness can be run on the server side and accept tasks issued by any client.- Asynchronous task delegation: issue long-consuming tasks, track progress, and return to view results at any time.- An isolation sandbox (container/VM) per task, supporting pre-installation toolchains and setup scripts.- Warehouse-aware execution: clone, open branches, run tests, lint, type checking; output verifiable terminal logs and test results.- Git workflow integration: create branches, commits and PRs, diffs and logs can be referenced and traced.- Task-level keys and network policies: no network access by default, explicit allowlist when needed.- Multi-task concurrency, with quota, scheduling and cancellation mechanisms.- The warehouse/organization/project-level memory file (
AGENTS.mdor equivalent) takes effect across runs.- Completely self-hosted: single-node Docker, multi-node cluster, or your own Kubernetes deployment is available, without relying on any SaaS.
- Share the same identity/account between Waz terminal, standalone TUI, IDE plug-in and web UI.- Session relay: Start the task on the Web and continue it in the terminal; or hand over the terminal session to the desktop for review.- Background Agent and multi-Agent team: Lead Agent disassembles tasks and distributes them to concurrent sub-Agents.- Routines: Timing/API call/warehouse events/CI/Issue tracker event trigger tasks.- Inbound Channels: Push tasks into Harness from Slack / Discord / Telegram / Webhook.- Outbound integrations: GitHub/GitLab/Gitea, Issue tracker, CI, MCP server, code review.- Remote operation observability: real-time logs, intermediate diff, intervention and cancellation during operation.- Sessions/tasks can share links with permission scope for team review.- End-to-end open source: Harness, sandbox runtime, web UI, integrations are all self-hosted.
This roadmap only represents the current exploration direction and will be adjusted based on actual implementation and community feedback.