The goal is to provide a web interface for a colony with some control of resources.
When ready it's intended to run as a container that is managed by the colonies CLI. If you want to run it now you have to start a dev server locally.
Every RPC call is logged in the browser console along with the time it took to get a response.
🔐 RPC Request
Key type: colony
Body: {
"msgtype": "getexecutorsmsg",
"colonyname": "cop-pilot",
"count": 100
}
✅ RPC Response received in 857.00ms
🔐 RPC Request
Key type: colony
Body: {
"msgtype": "getprocessesmsg",
"colonyname": "cop-pilot",
"count": 100,
"state": 1
} colony.ts:72:17
✅ RPC Response received in 864.00ms
🔐 RPC Request
Key type: colony
Body: {
"msgtype": "getprocessesmsg",
"colonyname": "cop-pilot",
"count": 100,
"state": 0
}This was created with Claude code
- Colony visualization
- Follow process after submission (websocket)
- Node.js (v18 or later)
- npm, pnpm, or yarn
-
Install dependencies:
npm install
-
Configure environment variables: Create a
.envfile with your Colony server configuration. Note: All environment variables must be prefixed withVITE_to be accessible in the client-side code:# Colony Server VITE_COLONIES_SERVER_HOST=colony-hostname VITE_COLONIES_SERVER_PORT=443 VITE_COLONIES_SERVER_TLS=true VITE_COLONIES_SERVER_PRVKEY=server-private-key VITE_COLONIES_COLONY_NAME=colony-name VITE_COLONIES_COLONY_PRVKEY=colony-private-key VITE_COLONIES_PRVKEY=user-private-key # Optional: S3 Configuration VITE_AWS_S3_ENDPOINT=s3-endpoint VITE_AWS_S3_ACCESSKEY=access-key VITE_AWS_S3_SECRETKEY=secret-key VITE_AWS_S3_REGION= VITE_AWS_S3_BUCKET=bucket-name VITE_AWS_S3_TLS=true VITE_AWS_S3_SKIPVERIFY=false
-
Start the development server:
npm run dev
-
Access the dashboard: Open http://localhost:5173 in your browser


