Gimil connects three layers:

Startup UI/API ---> Gimil Control Plane (Convex) ---> Enterprise Runner | | | | | | +--------------------------+-------------------------------+--> PRs + reports

• Startup team requests a mission
• Enterprise runner executes in a sandbox

• Startup ↔ Enterprise bridge with scoped API keys
• Mission queueing and run tracking
• HTTP endpoints for automation and integrations
• UI for API key provisioning and monitoring

npm install

npx convex dev

cd web VITE_CONVEX_HTTP_URL=""
VITE_INTEGRATION_ADMIN_KEY=""
npm run dev

Open /dashboard/api-keys to create keys, and use the draggable >_ bubble to submit missions.

• GET /health – service health check
• POST /demo/bootstrap – create demo startup + enterprise + integration
• POST /api-keys/create – issue a key
• POST /api-keys/list – list keys
• POST /integrations/run – queue a mission run (requires API key)

• Startup bubble: where product teams request missions and approve PRs
• Enterprise bubble: where the runner operates with sandboxed access to legacy systems
• API key scopes: restrict what actions a key can perform
• Runs: every mission is logged and tracked in integrationRuns

Gimil/ +-- web/ # Vite dashboard +-- agents/ # Agent orchestration scripts

1. Create API key in /dashboard/api-keys
2. The run is queued and tracked in Convex

MIT