JoeGlenn1213/ActionD

**Local AI Action Execution Engine for LGH (Local Git Hub)**
English | 简体中文
ActionD is a lightweight local CI/CD engine designed for AI agents. It listens to Git events from LGH and automatically triggers plugins to run code checks, tests, builds, and more.
Features
- 🔌 **Dynamic plugin discovery** — plugins are discovered automatically via manifest.json, no code changes required
- 🤖 **MCP integration** — a built-in MCP server lets AI assistants query and control CI/CD directly
- 📡 **Event-driven** — reacts to git.push, git.tag, and other LGH events
- 🖥️ **Web console** — live monitoring dashboard at http://localhost:3000
- 🔄 **Real-time streaming output** — live logs over SSE (Server-Sent Events)
- ⚡ **Hot reload** — reload plugins without a restart
- 🔄 **End-to-end workflow** — dev_cycle_run does it all in one call: commit → CI → results
- ⏮️ **Rollback** — automatically roll back to the previous commit on failure
Terminology
- **Job** — one CI/CD execution record produced when a plugin reacts to a Git event. Some tool names (actiond_action_get, actiond_actions_list) carry the legacy word *action*; it refers to the same object as the actiond_job_* tools.
- **Plugin** — the executable unit registered via manifest.json that runs on trigger events (git.push, git.tag); one plugin run yields one job.
- **Profile** — the CI scope preset (fast / full / release) controlling which plugins run per push.
Installation
macOS / Linux (Homebrew)
Install LGH the same way (brew install JoeGlenn1213/tap/lgh) — ActionD listens to its git events.
> The builtin plugin bundle (30+ check plugins) is **embedded in the binary**. actiond setup materializes it into ~/.localgithub/plugins, so a Homebrew or release-download install runs the same checks as a source checkout — no extra asset download needed. The web console is optional: without it the API still runs (see actiond-web or pass --web-dir).
Prerequisites
- Go 1.25+ (only when building from source)
- Python 3.8+ (used by plugins)
- LGH running locally
Build from source
> Note: ActionD uses SQLite for storage (the pure-Go modernc.org/sqlite build) — no CGO is needed and make build cross-compiles freely.
Quick Start
1. One-command setup (recommended)
If this is your first run, use setup to install the builtin plugin bundle (embedded in the binary), check dependencies, create the directory layout, and verify the environment:
Re-running setup is safe: already-installed plugins and your local edits are never overwritten (use --force to reset them to the bundled version, --skip-plugins to skip installation entirely).
To also start the daemon in the background right after setup:
2. Start the service and check it
3. Open the web console
Default directories and auto-detection
- Plugin directories are probed in order:
/plugins → /plugins → ~/.localgithub/plugins
- Web static assets are auto-detected in common locations; the recommended target is publishing ActionD-Web's out/ to:
~/.localgithub/actiond-web/out
- Without an explicit --repo-root, ActionD resolves repositories through LGH mappings first, then falls back to current-directory semantics.
CLI Commands
| Command | Description |
|------|------|
| actiond setup | One-command environment initialization (v1.2+) |
| actiond start | Start in the foreground |
| actiond start -d | Start as a background daemon |
| actiond stop | Stop the daemon |
| actiond restart | Restart the service (v1.2+) |
| actiond status | Show run status + directory info (v1.2+) |
| actiond plugins restore-go | Re-enable the Go verification plugins |
| actiond log | View server logs |
| actiond doctor | Diagnose system dependencies (tiered checks) |
| actiond version | Print version information |
| actiond mcp | Start the MCP server |
One-command setup (v1.2+)
Recommended on first install:
This automatically:
- Creates the directory layout (~/.localgithub/*)
- Checks dependencies (Git, Python, Go, Node)
- Detects web assets and plugin directories
- Verifies the LGH connection
Doctor
Runs 8 categories of tiered checks: