Snider 61e01bfdf1 feat: initial go-agent — agentci + jobrunner + plugins marketplace

Consolidates three codebases into a single agent orchestration repo:

- agentci (from go-scm): Clotho dual-run verification, agent config,
  SSH security (sanitisation, secure commands, token masking)
- jobrunner (from go-scm): Poll-dispatch-report pipeline with 7 handlers
  (dispatch, completion, auto-merge, publish draft, dismiss reviews,
  send fix command, tick parent epic)
- plugins marketplace (from agentic/plugins): 27 Claude/Codex/Gemini
  plugins with shared MCP server

All 150+ tests passing across 6 packages.

Co-Authored-By: Virgil <virgil@lethean.io>

2026-02-21 15:47:19 +00:00

3.3 KiB

Raw Permalink Blame History

name

description

args

flags

status

Check Coolify deployment status via browser or API

project-or-service

api

team

description	type	default
Use API instead of browser automation	boolean	false

description	type	default
Team to query (default Agentic)	string	Agentic

Check Coolify Status

Query deployment status for projects, services, and resources.

Usage

/coolify:status                     # View all projects
/coolify:status "Software Staging"  # View specific project
/coolify:status --api               # Use API instead of browser

Browser Automation (Preferred)

1. Load Tools

ToolSearch: select:mcp__claude-in-chrome__tabs_context_mcp
ToolSearch: select:mcp__claude-in-chrome__computer
ToolSearch: select:mcp__claude-in-chrome__read_page

2. Navigate to Projects

# Default to localhost (local dev instance)
COOLIFY_URL="${COOLIFY_URL:-http://localhost:8000}"

mcp__claude-in-chrome__tabs_context_mcp(createIfEmpty: true)
mcp__claude-in-chrome__navigate(tabId, url: "$COOLIFY_URL/projects")

3. Read Project List

mcp__claude-in-chrome__computer(action: "screenshot")

4. Check Specific Project

Click project name
Click environment (usually "production")
View service cards with status indicators

Status Indicators

Indicator	Meaning
🟢 Green dot	Running (healthy)
🔴 Red dot	Exited / Failed
🟡 Yellow dot	Deploying / Starting
⚪ Grey dot	Stopped

View Service Details

Click service card
Check tabs:
- Configuration - General settings
- Logs - Container output
- Links - Access URLs

API Method

List All Resources

# Set Coolify URL and token
COOLIFY_URL="${COOLIFY_URL:-http://localhost:8000}"
TOKEN="your-api-token"

# List servers
curl -s -H "Authorization: Bearer $TOKEN" "$COOLIFY_URL/api/v1/servers" | jq

# List projects
curl -s -H "Authorization: Bearer $TOKEN" "$COOLIFY_URL/api/v1/projects" | jq

# List services (one-click apps)
curl -s -H "Authorization: Bearer $TOKEN" "$COOLIFY_URL/api/v1/services" | jq

# List applications
curl -s -H "Authorization: Bearer $TOKEN" "$COOLIFY_URL/api/v1/applications" | jq

# List databases
curl -s -H "Authorization: Bearer $TOKEN" "$COOLIFY_URL/api/v1/databases" | jq

Get Specific Resource

# Get service by UUID
curl -s -H "Authorization: Bearer $TOKEN" "$COOLIFY_URL/api/v1/services/{uuid}" | jq

# Get service logs
curl -s -H "Authorization: Bearer $TOKEN" "$COOLIFY_URL/api/v1/services/{uuid}/logs" | jq

SSH Verification (Advanced)

For direct container verification when API/UI insufficient:

# SSH to Coolify server
ssh user@your-coolify-host

# List all containers
docker ps --format 'table {{.Names}}\t{{.Status}}'

Response Fields (API)

Field	Description
`uuid`	Unique identifier
`name`	Resource name
`status`	running, stopped, deploying, failed
`fqdn`	Fully qualified domain name
`created_at`	Creation timestamp
`updated_at`	Last update timestamp

Team Switching

In browser, use team dropdown in top navigation:

Click current team name (e.g., "Agentic")
Select target team from dropdown
Resources will reload for selected team

API tokens are team-scoped - each token only sees its team's resources.

3.3 KiB Raw Permalink Blame History