aidevops Agent工作流

Requirements and Platform Support

aidevops itself is mostly Markdown, shell, Python, and TypeScript/Bun tooling. Most software, infrastructure, research, and operational workflows use cloud models and do not require a local GPU. Media generation, local models, creative applications, simulators, and voice pipelines have their own optional hardware and platform requirements.

The framework is developed primarily on macOS and includes Linux support for documented workflows. Individual tools may require a specific operating system, architecture, desktop application, licence, API account, or human-present authorization. Check platform support and capability readiness before installation or execution.

Common command-line dependencies are discovered by setup rather than assumed. git, curl, jq, fd, and ripgrep cover many core workflows; optional tools are installed or configured only through their documented, consent-aware paths.

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

brew install marcusquinn/tap/aidevops && aidevops update   # macOS (Homebrew)
npm install -g aidevops && aidevops update                 # Linux / cross-platform

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.

Installation

Direct installer

bash <(curl -fsSL https://aidevops.sh/install)

Installation or PATH problems

aidevops status
aidevops doctor
aidevops update

Quick Start

For the full first-run checklist (providers, project layout, automation), see Quick Setup.

1. Install aidevops using one of the methods above.
2. Start OpenCode in a project and run /onboarding for account-level setup.
3. Run aidevops init inside the repository.
4. Run /setup-git when the repository needs platform-specific secrets or workflows.
5. Describe the outcome you want, or use /skills recommend "TASK" to discover a route.

Initialize selected features when a repository needs less than the default set:

aidevops init planning
aidevops init planning,git-workflow,code-quality
aidevops init deployment-context
aidevops init wordpress-context

Depending on selected features and existing files, initialization can add:

- .aidevops.json for repository feature and workflow metadata. - .agents/AGENTS.md for project-specific AI guidance. - TODO.md and todo/ for tasks, plans, PRDs, and verification state. - DESIGN.md for repositories with a detected interface. - context/keywords.md search targets (keywords, AI-answer questions, entities) for standard-scope repositories; public repositories keep the data in a private team hub (standard). - Deployment and WordPress context manifests when explicitly selected. - Standard project courtesy files only when they do not already exist.

Repository registration lives in ~/.config/aidevops/repos.json; updates can then check initialized projects for framework and template drift.

Configuration

aidevops config list
aidevops config validate
aidevops config set updates.auto_update false

Precedence is AIDEVOPS_* environment variables, then user configuration, then built-in defaults. Store secrets with aidevops secret; do not put credential values in committed templates, command arguments, logs, or AI conversations.

OpenCode Go subscription: create an API key in your OpenCode account first

opencode auth login # choose "OpenCode Go", paste the key

NanoGPT: create an API key in your NanoGPT account first

opencode auth login # choose "NanoGPT", paste the key

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

Integrations and Extensibility

aidevops combines CLI tools, shell/Python/TypeScript helpers, direct APIs, OpenAPI exploration, browser automation, and on-demand MCP servers. MCPs remain disconnected until an approved specialist needs them, reducing idle processes, tool-schema context, and accidental authority.

Integration families include:

• GitHub, GitLab, Gitea, Forgejo, CI systems, quality platforms, and dependency scanners.
• Hosting, DNS, cloud, deployment, object storage, networking, monitoring, and local development.
• Product analytics, error monitoring, email, communications, social platforms, outreach, and payments.
• Accounting, ecommerce, WordPress (including Rank Math SEO MCP), documents, OCR, browser automation, and creative applications.
• Context7, exact code search, OpenAPI search, local models, and model-provider account pools.

Common Workflows

Runtime command names may be namespaced, such as /aidevops-full-loop, where a client reserves or groups slash commands differently. OpenCode exposes main agents in its agent picker.

Troubleshooting