- Go 33.8%
- Shell 33.1%
- CSS 11.9%
- JavaScript 11.7%
- Python 4.1%
- Other 5.4%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
Some checks failed
Triage / triage-pr (push) Has been skipped
Triage / triage-issue (push) Has been skipped
Triage / scheduled-health-check (push) Has been skipped
Triage / manual-operation (push) Has been skipped
jbcom Gardener / Discover Organizations (push) Has been cancelled
jbcom Gardener / Gardening Report (push) Has been cancelled
Go CI / Lint (push) Has been cancelled
Go CI / Test (push) Has been cancelled
Go CI / Build (push) Has been cancelled
Go CI / Docker Scout Analysis (push) Has been cancelled
Release Please / release-please (push) Has been cancelled
Triage / rebase-prs-on-main-push (push) Has been cancelled
Bumps the github-actions group with 1 update: [github/codeql-action](https://github.com/github/codeql-action).
Updates `github/codeql-action` from 4.31.10 to 4.32.0
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](
|
||
| .crew | ||
| .cursor | ||
| .github | ||
| actions | ||
| branch-rulesets | ||
| cmd/control-center | ||
| docs | ||
| enterprise | ||
| global-sync/.github | ||
| memory-bank | ||
| packages | ||
| pkg | ||
| professor-pixels-arcade-academy/.crew | ||
| repository-files | ||
| schemas | ||
| scripts | ||
| strata/.crew | ||
| sync-files | ||
| .gitignore | ||
| .golangci.yml | ||
| .goreleaser.yaml | ||
| .pre-commit-config.yaml | ||
| .release-please-manifest.json | ||
| action.yml | ||
| agentic.config.json | ||
| AGENTS.md | ||
| bulk_delegation_status.md | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| commitlint.config.js | ||
| CONTRIBUTING.md | ||
| COVERAGE.md | ||
| doc.go | ||
| DOCKER-HUB-MIGRATION.md | ||
| Dockerfile | ||
| entrypoint.sh | ||
| epic-349-plan.md | ||
| fix_shas.py | ||
| go.mod | ||
| go.sum | ||
| IMPLEMENTATION-COMPLETE.md | ||
| IMPLEMENTATION-SUMMARY.md | ||
| JBCOM_CONTROL_CENTER_AGENT_USE.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| release-please-config.json | ||
| repo-config.json | ||
| repos_list.txt | ||
| TESTING.md | ||
| triage-hub.json | ||
Control Center
Enterprise AI orchestration for the jbcom ecosystem.
Overview
Control Center is a unified CLI tool for managing AI agents, repository synchronization, and enterprise workflows across the jbcom ecosystem. It provides native integrations with:
- Ollama (GLM 4.6 Cloud) - Fast code review and analysis
- Google Jules - Multi-file refactoring with auto-PR creation
- Cursor Cloud Agent - Long-running autonomous tasks
Installation
Go Install
go install github.com/jbcom/control-center/cmd/control-center@latest
Docker
docker pull jbcom/control-center:latest
Binary
Download from Releases.
Commands
Gardener
Enterprise-level cascade orchestrator. Discovers organizations, auto-heals control centers, processes backlog, and cascades instructions.
# Run for all organizations
control-center gardener --target all
# Run for specific organization
control-center gardener --target extended-data-library
# Dry run
control-center gardener --target all --dry-run
Curator
Nightly triage of issues and PRs. Analyzes and routes to appropriate AI agents.
# Curate a specific repository
control-center curator --repo jbcom/control-center
# Dry run
control-center curator --repo jbcom/control-center --dry-run
Reviewer
AI-powered code review using Ollama.
# Review a specific PR
control-center reviewer --repo jbcom/control-center --pr 123
# With debug output
control-center reviewer --repo jbcom/control-center --pr 123 --log-level debug
Fixer
Automated CI failure resolution.
# Analyze and suggest fix for a PR
control-center fixer --repo jbcom/control-center --pr 123
# Analyze a specific workflow run
control-center fixer --repo jbcom/control-center --run-id 12345678
GitHub Action
Control Center is distributed as a Docker-based GitHub Action. All actions pull the Docker image from Docker Hub at runtime.
Basic Usage
Use Control Center in your workflows:
- uses: jbcom/control-center@v1
with:
command: reviewer
repo: ${{ github.repository }}
pr: ${{ github.event.pull_request.number }}
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
OLLAMA_API_KEY: ${{ secrets.OLLAMA_API_KEY }}
Specific Command Actions
Or use specific command actions for simpler interface:
# AI Code Review
- uses: jbcom/control-center/actions/reviewer@v1
with:
repo: ${{ github.repository }}
pr: ${{ github.event.pull_request.number }}
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
OLLAMA_API_KEY: ${{ secrets.OLLAMA_API_KEY }}
# CI Failure Analysis
- uses: jbcom/control-center/actions/fixer@v1
with:
repo: ${{ github.repository }}
run_id: ${{ github.run_id }}
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
OLLAMA_API_KEY: ${{ secrets.OLLAMA_API_KEY }}
# Nightly Triage
- uses: jbcom/control-center/actions/curator@v1
with:
repo: ${{ github.repository }}
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
GOOGLE_JULES_API_KEY: ${{ secrets.GOOGLE_JULES_API_KEY }}
CURSOR_API_KEY: ${{ secrets.CURSOR_API_KEY }}
Direct Docker Usage
You can also run Control Center directly via Docker:
# Pull the image
docker pull jbcom/control-center:latest
# Run a command
docker run --rm \
-e GITHUB_TOKEN="$GITHUB_TOKEN" \
-e OLLAMA_API_KEY="$OLLAMA_API_KEY" \
jbcom/control-center:latest \
reviewer --repo owner/repo --pr 123
Version Pinning
Recommended: Use floating major version tags for automatic updates:
- uses: jbcom/control-center@v1 # Latest v1.x.x
Stable: Pin to minor version for controlled updates:
- uses: jbcom/control-center@v1.1 # Latest v1.1.x
Locked: Use exact version for reproducibility:
- uses: jbcom/control-center@v1.1.0 # Exact version
Inputs
| Input | Description | Required | Default |
|---|---|---|---|
command |
Command: gardener, curator, reviewer, fixer | Yes | - |
repo |
Target repository (owner/name) | No | - |
pr |
Pull request number | No | - |
target |
Target for gardener | No | all |
dry_run |
Run without making changes | No | false |
log_level |
Log level: debug, info, warn, error | No | info |
Configuration
Environment Variables
| Variable | Description |
|---|---|
GITHUB_TOKEN |
GitHub token for API access |
CI_GITHUB_TOKEN |
Alternative GitHub token (CI workflows) |
OLLAMA_API_KEY |
Ollama Cloud API key |
GOOGLE_JULES_API_KEY |
Google Jules API key |
CURSOR_API_KEY |
Cursor Cloud Agent API key |
Config File
Control Center looks for configuration in:
--configflag$HOME/.control-center.yaml./.control-center.yaml/etc/control-center/config.yaml
Example:
log:
level: info
format: text
gardener:
target: all
decompose: false
backlog: true
curator:
repo: jbcom/control-center
Architecture
control-center/
├── cmd/control-center/ # CLI entrypoint
│ └── cmd/ # Cobra commands
│ ├── root.go
│ ├── gardener.go
│ ├── curator.go
│ ├── reviewer.go
│ ├── fixer.go
│ └── version.go
├── pkg/
│ ├── clients/ # API clients
│ │ ├── ollama/ # Ollama GLM 4.6
│ │ ├── jules/ # Google Jules
│ │ ├── cursor/ # Cursor Cloud Agent
│ │ └── github/ # GitHub API + gh CLI
│ ├── config/ # Configuration
│ └── orchestrator/ # Orchestration logic
├── Dockerfile
├── action.yml # GitHub Action
├── .goreleaser.yml # Release config
└── .golangci.yml # Linter config
Task Routing
The Curator automatically routes tasks to the appropriate AI agent:
| Task Type | Agent | Reason |
|---|---|---|
| Quick fix (<5 lines) | Ollama | Fast, inline |
| Multi-file refactor | Jules | Async, AUTO_CREATE_PR |
| Complex debugging | Cursor | Full IDE context |
| Documentation | Jules | Full file context |
| Ambiguous/sensitive | Human | Requires judgment |
Development
Prerequisites
- Go 1.23+
- Docker (optional)
- gh CLI (for GitHub operations)
Build
go build -o control-center ./cmd/control-center
Test
go test -v ./...
Lint
golangci-lint run
Release
Releases are automated via GoReleaser on tag push:
git tag v1.0.0
git push origin v1.0.0
License
MIT License - see LICENSE for details.
Related Projects
- secretssync - Multi-account secrets management
- vendor-connectors - Python API clients
Built with ❤️ by the jbcom ecosystem