Coding sessions
Keep coding context and implementation results linked to the relevant Vaiz task.
Keep coding context and implementation results linked to the relevant Vaiz task.
Keep coding context and implementation results linked to the relevant Vaiz task.
Key capabilities
See each run on the task from start to finish.
Agents open pull requests that link back to the task.
Keep working with the same agent without starting over.
When a run ends, Vaiz saves what was done as a session log, so the next agent or teammate starts with context.
Each run posts updates to the task comments: when it started, which pull request it opened, and a summary of the result. Task history shows who delegated the work and how the run ended, so reviewers see the full story next to the code.
When you work in Claude Code, Cursor, or Codex through the Vaiz MCP server, the agent loads the task context before it starts and saves a devlog when it finishes: commits, linked pull requests, decisions, and problems it ran into. The devlog appears in Space Memory next to the task and shows which tool wrote it.
A run of a cloud coding agent on a Vaiz task. It starts when you delegate the task, and the task shows its status, branch, pull request, and result.
Cursor cloud agents and Claude managed agents. Delegate a task to start a session.
The agent posts a summary to the task comments and links its pull request to the task. If Space Memory is on, the session log is saved there too.
Yes. Send a follow-up from the session menu or reply to the agent's comment in the task.
GitHub repositories. Connect GitHub to Vaiz to link pull requests to tasks.
Start a free trial, set up your first project in minutes, and invite your team when you’re ready.