marcusquinn/aidevops

**aidevops.sh** is an OpenCode
plugin and AI DevOps framework for carrying work from intent to a verified
outcome. It combines specialist agents, durable repository knowledge, safe Git
workflows, model routing, operational automation, and service integrations for
software, infrastructure, business, marketing, content, research, and creative
production.
Instead of treating every job as an isolated chat, aidevops gives people and AI
agents a shared operating system: the right context is loaded on demand, work is
isolated, consequential actions are gated, evidence is retained, and useful
lessons improve later work.
**One conversation, autonomous project delivery, with security, teamwork,
token efficiency, and quality control built in.**
The Aim
**Maximum useful value for your time and money.** aidevops is built for the gap
between “the model can probably do this” and “the work is done, verified, safe,
and worth the cost.”
- Load focused guidance only when it is relevant.
- Match model capability and reasoning effort to the work.
- Explore optional Jev structured decisions
with reversible retrieval and shadow-triage pilots,
private evaluation reports and bounded continuation examples; no default routing,
runtime hooks or compaction changes.
- Keep secrets, protected data, and private state out of chat and Git.
- Let people and agents work in parallel without sharing unsafe mutable state.
- Preserve tasks, plans, decisions, evidence, and progress in durable sources of truth.
- Detect stuck work, failing automation, review traps, and repeated friction.
- Turn observed lessons into better guidance, checks, helpers, and follow-up work.
- Reserve human attention for taste, authority, secrets, and consequential ambiguity.
The “100x more capable” goal is an ambition to substantiate, not a guaranteed or
measured result. The canonical purpose and decision criteria are in
.agents/aidevops/purpose.md.
Quick Setup
New to aidevops? Work through these six steps once, in order, so nothing is
missed. Commands are safe to rerun. For a guided version, type /onboarding in
an AI session after step 2.
1. Install aidevops
Setup deploys agents to ~/.aidevops/agents/, installs and configures
OpenCode, and offers optional tools. Accept **Tabby** when offered. Other
methods: Installation. Check the result with
aidevops status; aidevops doctor --fix resolves duplicate installs and PATH
conflicts.
2. Open Tabby and start OpenCode
Rerun aidevops tabby sync after adding projects in step 4. Profile details:
Tabby profiles.
3. Connect model providers
Inside OpenCode, /connect is equivalent to opencode auth login. Add several
accounts per provider so the pool can rotate on rate limits, then restart
OpenCode. Never paste keys or tokens into an AI chat; store other service
credentials with aidevops secret set NAME.
4. Put projects in ~/Git on the local drive
Keep canonical clones on the local disk, not in a cloud-synced folder such as
iCloud Drive, Dropbox, or OneDrive. Layout: personal repositories at
~/Git/ , organization or third-party repositories at
~/Git/ / (repository organization).
Already-registered repositories in an older layout can use the guarded
aidevops repos migrate-layout plan instead of a manual move.
5. Turn on auto-update, Pulse, workers, and routines
Pulse runs every 2 minutes and dispatches headless workers only for repositories
marked "pulse": true in ~/.config/aidevops/repos.json; enable it only where
autonomous work is approved. Workers pick up issues labelled auto-dispatch.
Pause with aidevops pulse stop. In an AI session, use /routine to design
recurring jobs, /pulse to supervise, and /runners for runner setup. Details:
routines,
worker diagnostics.
6. Verify and start working
Then, in OpenCode inside a project:
Quick Reference
- **Install:** npm install -g aidevops && aidevops update
- **Recommended runtime:** OpenCode; Claude Code and Codex CLI are supported interactive runtimes
- **Entry points:** aidevops, ~/.aidevops/agents/AGENTS.md, runtime commands and skills
- **Default development agent:** Build+
- **Routing:** provider-neutral simple, standard, and thinking workload tiers
- **Core lifecycle:** understand → isolate → implement → verify → PR → authority-aware merge/release
- **Agent sandbox backends:** Apple container (opt-in executable); Firecracker Linux KVM (host probe only, not yet executable)
- **Primary sources:** user guide, domain index, architecture, configuration
Essential commands
For a registered repository whose GitHub Actions cannot run, record