01
Workspace
Issues, projects, cycles, views, events, and Change Requests shaped for software teams.
Product
A project system where agent work becomes a structured run.
xmode keeps the familiar shape of software delivery while giving teams an operating surface for objectives, plans, skills, actions, sandboxes, evidence, and review.
Core surfaces
Three surfaces, one auditable loop.
The project workspace gives context, the catalog defines trusted behavior, and the run workbench shows what actually happened.
02
Catalog
Versioned skills, actions, and pipelines with schemas, defaults, evidence rules, and release history.
03
Structured run chat
A pipeline execution surface for decisions, follow-ups, goal checks, approvals, and progress.
04
Sandbox workbench
Visible files, commands, logs, artifacts, diffs, and runtime state for every code-changing run.
05
Integrations
GitHub App, GitLab, private repository sync, signed event intake, SSO, and future provider adapters.
06
Change Requests
Every code-changing run opens a new branch and a provider-neutral review package.
Execution path
From issue to reviewed Change Request.
Plan with context
The run starts from a project, issue, event, or manual objective. If the objective is unclear, the pipeline can ask for a plan or a follow-up answer.
Execute through versioned playbooks
Skills describe best practices. Actions bind those skills to providers, runtime policy, schemas, and evidence expectations.
Inspect the sandbox
Teams can review files, terminal commands, artifacts, structured outputs, and diffs before accepting the result.
Publish the review package
GitHub PRs and GitLab MRs map into a single Change Request model with run context attached.
Interactive pipeline runs
Decision trees without hiding the conversation.
Authors define reusable pipeline policy. Users experience it as a structured conversation that can ask, branch, pause, resume, or escalate.
xmode
Which implementation path should this run take?
Minimal fix
Refactor module
Ask for plan
Sandbox
Created isolated worktree, ran tests, captured artifacts, and prepared a branch-backed Change Request.