Works with your stack, not around it
Aiva connects to the tools your team already runs — source control, CI/CD, tickets, a managed browser, preview environments, and anything you can reach over MCP — so agents work inside your existing workflow.
GitHub and Azure DevOps
Sessions start from your repositories and end as pull requests — using credentials scoped to your workspace.
Remote repository sessions
Clone or reuse cached copies of your repositories, start from any branch, and cut new ones from any base.
Pull request workflows
Guided commit and PR creation with configurable message prompts, reviewer assignment, and squash or merge strategies.
Your permissions, not ours
Source-control tokens are stored per workspace and used only for the repositories you connect. Nothing is shared across workspaces.
GitHub Actions and Azure Pipelines
CI results show up where the work happened — next to the session and the pull request that triggered them.
Run visibility
Workflow and pipeline runs appear alongside your sessions, with job and step detail when something needs a closer look.
Failure notifications
A failed run raises a notification tied to the session that caused it — so the agent, or you, can get straight to the fix.
Agents can read CI too
Agents inspect runs, jobs, and failing steps through Aiva's cloud tools and fix the build without you pasting logs.
Linear, Asana, GitHub Issues, Azure Boards
Connect your tracker to the workspace and sessions become part of the paper trail.
Tickets in context
Link a session to the work item it implements. Agents read the ticket, its comments, and its attachments for context.
Progress where your team looks
Agents search the backlog, create items, update states, and leave comments — through the provider you already use.
One integration per workspace
Configure the provider once at the workspace level. Every session and agent in the workspace gets the same view.
A real browser for your agents
Swarm Surf gives agents a managed cloud browser — no local Chrome, no flaky headless setup on your machine.
Browse, click, verify
Agents navigate, fill forms, take screenshots, and record sessions to validate the change they just made — like a person would.
Isolated per session
Each Aiva session gets at most one browser session of its own. Agents never see raw browser session ids or other sessions' tabs.
Workspace-enabled
Enable Swarm Surf per workspace with your own API key, stored encrypted in workspace settings.
Preview environments on demand
Agents deploy the branch they are working on to an isolated SideQuest environment and test against the real thing.
From branch to running app
Agents create, rebuild, and destroy preview environments for the repository they are working in — scoped to their own session.
Diagnose in place
Deploy logs, runtime logs, and exec access let agents debug the deployed environment without leaving the session.
Visible in the session
Environments created by a session show up in its chat widget, so you always know what is running and why.
Your internal tools, in the agent's hands
Attach workspace-scoped MCP servers and agents can use your internal services — admin APIs, data platforms, deployment tooling — alongside Aiva's built-in cloud tools for pull requests, tickets, browsing, and previews.
- Workspace-scoped configuration — add a server once, every session can use it
- Aiva's own cloud operations exposed to agents as MCP tools
- Every tool call recorded in the session transcript
agent → aivacloud_pm_add_comment
{
"item": "ENG-482",
"comment": "Fix implemented, PR #128 open — CI green."
}
agent → yourco_feature_flags.enable
{
"flag": "new-checkout",
"env": "staging"
}
Bring your stack
Connect source control, your tracker, and your tools — then let agents work the way your team already does.