AI AGENTS
Chat-Requested Shell-Gated Upgrade Agent
An engineer asks in chat to bump a named package; the agent pins the requested version, validates it in a sandboxed shell.
How it runs
The automated pipeline, trigger to output.
- TriggerChat request naming package and version
- ActionPin version, apply, and run tests in sandboxed shellShell
- LogicBranch on test pass or fail
- ActionOpen GitLab MR on successGitLab
- OutputReply in chat with MR link or failing test output
What it does
This agent turns a one-line chat request into a validated upgrade. An engineer names a package and target version; the agent pins it, proves it in a sandboxed shell, and answers in the same thread with an MR link or the precise failure that blocked it.
When to use it
Use it when developers want self-serve, on-demand dependency bumps without context-switching into a terminal. It removes the busywork of branching, installing, and running tests by hand.
How it works
- 1A chat message triggers the run with the package name and desired version.
- 2The agent pins the exact version, applies it in a sandboxed shell, and runs the test suite.
- 3A logic gate branches on the test result.
- 4On success it opens a GitLab MR and replies in-thread with the link and a short summary.
- 5On failure it replies with the failing test names and log tail so the requester can decide next steps.
Set it up
What you configure once, before turning it on.
- 1Connect ShellRun sandboxed commands inside the workspace.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.