Organization repository on GitHub
👨🏽💻 CaptainCore is a command line application for automating WordPress maintenance.
- Forks
- 11
- Last pushed
- Updated Oct 2026
Repo stats from the GitHub API, cached Oct 2026.Homepage
CommunityJev Agents & MCP
Captaincore
CaptainCore is a Go CLI built on Cobra that manages WordPress sites over SSH and WP-CLI: Restic backups to B2, git-backed quicksaves, parallel uptime checks, updates with before/after diffs, and a REST plus WebSocket server for remote dispatch.
- Stars
- 75
- Language
- Go
- License
- MIT
- Published by
- Community
- Author
- CaptainCore
- Last verified
- Oct 2026
About this project
CaptainCore is a WordPress management toolkit for hosting professionals. Built with Cobra in Go, it manages WordPress sites at scale via SSH and WP-CLI. Backups -- Incremental backups with Restic to B2 cloud storage. Quicksaves -- Git-based change tracking for plugins, themes, and config. Uptime Monitoring -- Parallel HTTP checks with SQLite-backed stats and email alerts. SSH Management -- Direct SSH and remote script execution across sites.
Quoted from the project's README. Read the full README.
Used inJev for Software & DevTools
- Languages
- Go
Highlights
- Jev shows up in two commands: `captaincore typesafe` for typed yes/no, choice and score answers, and `scan --triage` for ranking findings.
- Bulk work takes target groups, so `backup generate @all --fleet` and `update @production` run across many sites.
- The release installer verifies checksums and unpacks its own runtime scripts into ~/.captaincore, so nothing else is cloned.
- Documented external dependencies are Rclone for cloud sync, Restic for encrypted backups, and Git for quicksaves.
Watch out
Pairing requires a CaptainCore Manager site, a WordPress install with pretty permalinks and the CaptainCore Manager plugin active, and one `connect` handles both directions with no wp-config constants needed. Rclone, Restic and Git must be installed separately. A source checkout owns its own app/ and lib/ scripts, so `upgrade` and install.sh skip it and you update with git pull and a rebuild. The optional Jev key is `typesafe_api_key` in config.json or TYPESAFE_API_KEY in the environment; what triage does with the ranking and how it is tuned is not documented here, and releases target Linux and macOS on amd64, arm64 and armv7 with no Windows build mentioned. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
Not for the parts that need pairing. `captaincore connect --server-url=...` expects a CaptainCore Manager site, WordPress with pretty permalinks enabled and the CaptainCore Manager plugin active, and a single command fetches the Manager's CLI token and, with --server-url, registers this machine's address so the Manager can dispatch jobs to `captaincore server`. The README notes no wp-config constants are needed for it.
Two places, both narrow. `captaincore typesafe` takes state as text or JSON and asks typed yes/no, choice and score questions with no prose output, and `captaincore scan --triage` ranks findings produced by the native malware rule set. Both read `typesafe_api_key` from the per-tenant config.json, with TYPESAFE_API_KEY in the environment as an alternative.
The updater deliberately steps aside. A source checkout owns its own app/ and lib/ scripts, and both `captaincore upgrade` and install.sh detect the .git directory and leave it alone, so you update it with git pull and a rebuild. Building from source needs Go 1.25 or newer, while the release installer just downloads a platform build, verifies it against the release checksums and unpacks the runtime scripts itself.
Three external tools: Rclone for cloud storage sync, Restic for encrypted backups to B2, and Git for quicksave change tracking. The CaptainCore binary carries its own runtime scripts and unpacks them into ~/.captaincore on first run, so cloning is only needed if you want to build. A paired Manager site is the other prerequisite, and Kinsta and GridPane provider integrations are built in if you use them.
There is no scheduler of its own. Backups, quicksaves, updates and uptime checks all run from system cron, and docs.captaincore.io carries a reference crontab. What the CLI does provide is target groups, so backup generate @all --fleet runs across many sites in fleet mode and update @production scopes a batch to one group. Uptime checks are parallel HTTP requests with SQLite-backed statistics and email alerts.
Three layers. System config holds server paths, the master SSH connection and fleet mode. Per-tenant config holds API keys, cloud storage remotes for rclone, branding and the site list. Optional integrations cover fathom_api_key for analytics and typesafe_api_key for the decision API, with TYPESAFE_API_KEY in the environment as an alternative. Folder settings such as path, path_tmp, path_recipes, path_scripts, path_keys and logs default to folders under ~/.captaincore when left blank.
One captaincore connect handles both directions. It fetches the Manager's CLI token and, with --server-url, registers this machine's address so the Manager can dispatch jobs to captaincore server, with no wp-config constants needed. That server is a REST plus WebSocket API, and everything else talks to sites over SSH and WP-CLI: site list, ssh, backup generate, quicksave generate, monitor and update. Kinsta and GridPane provider APIs are built in.
More Jev resources like this
118GitHub stars
A Claude Code skill that moves bulk judgment off Claude and onto Jev. You filter files, classify items, rank candidates or locate lines, and it returns typed verdicts, a shortlist with borderline markers, and a receipt of the tokens Claude did not read.
Jev Agents & MCP#community#jevbest
Community
UditAkhourii/quicksilverJavaScript
UditAkhourii/quicksilverJavaScript36GitHub stars
Pi extension that strips the full Agent Skills catalog from every request and loads only the skills a Jev ranking call judges relevant.
Jev Agents & MCP#community#jevbest#catalog-import
102GitHub stars
Behavioral code search that asks Jev to score repository fragments for a plain-language question and returns exact excerpts with paths and lines.
Jev Agents & MCP#community#jevbest#catalog-import
Community
nassim-arifette/jevgrepTypeScript
nassim-arifette/jevgrepTypeScript72GitHub stars
MCP server over stdio that gives coding agents fourteen Jev judgment tools, turning evidence plus an enumerable question into auto, review, or escalate actions from calibrated probabilities.
Jev Agents & MCP#community#jevbest#catalog-import
Community
PyModel/jev-judge-mcpPython
PyModel/jev-judge-mcpPython35GitHub stars
Diff-aware test selector that sends the git diff to Jev with one question per test, then prints the native filter flags and hands them to vitest, jest, node, bun, Playwright, cargo, or go test.
Jev Agents & MCP#community#jevbest#catalog-import
Community
mizchi/jev-test-filterTypeScript
mizchi/jev-test-filterTypeScript16GitHub stars
Shell wrapper that intercepts unknown subcommands, reads the target CLI help output, and asks Jev which documented subcommand matches the intent behind the typo.
Jev Agents & MCP#community#jevbest#catalog-import
Community
syumai/jevyoumeanGo
syumai/jevyoumeanGoFrom the Jev community
Posts from builders shipping with Jev right now.