Integrations

It works through the systems you already use.

Each integration grants a named set of capabilities, and a role can use only the ones its file grants. In paper mode every one of them is a mock that remembers what was done to it.

Adapters

What each one lets an agent do.

Code and delivery

GitHub
Reads the code, opens and updates changes, files items, and merges once the merge gate is approved.
read_codeopen_changeupdate_changemerge_changecreate_item
GitHub Actions
Runs builds and test suites, and reads back what passed and what did not.
run_buildrun_testsread_test_results
Vercel
Reads where each release stands, rolls back to the last good one, and switches a flag off.
read_release_staterollbackset_flag
GitLab
GitLab.com or your own GitLab: reads the code, opens merge requests, runs pipelines, files issues, and merges once the merge gate is approved.
read_codewrite_filesopen_changeupdate_changemerge_changeread_change_feedbackrun_buildread_test_resultsread_itemscreate_itemupdate_itemsync_state· Coming
Jira
Reads issues and their comments as data, files new ones and notes progress on them.
read_itemscreate_itemupdate_itemsync_state· Coming
Linear
Reads issues as data, files new ones and notes progress on them.
read_itemscreate_itemupdate_itemsync_state· Coming

Mobile

Expo EAS
Builds the app, reads test results and release state, rolls back an update, and can halt a rollout.
run_buildread_test_resultsread_release_staterollbackhalt_rollout
App Store Connect
Reads release state and reviews, and can halt a phased release.
read_release_stateread_reviewshalt_rollout
Google Play
Reads release state and reviews, and can halt a staged rollout.
read_release_stateread_reviewshalt_rollout

Watching production

Sentry
Alerts, logs and metrics — what SRE reads to notice breakage before users do.
read_alertsread_logsread_metrics
PostHog
Product usage, so Analytics can say whether a change delivered what it claimed.
read_usage
Datadog
Monitors, logs and metrics, on any Datadog site — the same reads SRE takes from Sentry.
read_alertsread_logsread_metrics

People

Intercom
Tickets and reviews for Support to draft replies to — read as data, never as instructions. Nothing is sent until a person approves it.
read_ticketsread_reviewsdraft_reply
Slack
Posts what agents did to your channel. From Slack, anyone can pause every agent, list open incidents or ask SRE to investigate.
post_messageopen_gate_thread· Coming
Microsoft Teams
Posts what agents did to a Teams channel, through its incoming webhook.
post_message
PagerDuty
Pages whoever is on call when an incident opens, and resolves it when it closes.
x_trigger_incident· Comingx_resolve_incident· Coming

Need a system that is not listed here? Send us a message, or write to us at admin@omnirecursivelabs.com.

Packs

Any product is accepted. What differs is how deep agents may go.

A pack recognises a kind of product and knows its build, its tests, its release and what to watch. Where none claims a component, the generic pack does.

web
Web
Websites and web applications, with their build, tests and deploy target.
mobile
Mobile
iOS and Android apps, their store tracks and over-the-air updates.
servicenow
ServiceNow
Scoped applications on an instance, with instance scans and upgrade checks.
library
Package
Libraries others depend on, with downstream watch and deprecation review.
generic
Generic
Everything else. Capped at the shallowest depth and never deploying — accepted, not refused.

Credentials

Three scopes, so each key lives where it belongs.

A project uses the nearest credential there is — its own, then its workspace's, then the deployment's — and a saved secret shows only a fingerprint, never itself.

01Project
02Workspace
03Platform

Start in paper mode. Go live when you mean it.

Every integration is mocked until you add credentials, so you can watch the whole organization work on your product before it touches a real system.

Or write to us directly: admin@omnirecursivelabs.com