Orchestrate agents
across every device

Local-first agent coordination with end-to-end encryption. Plan, build, and ship with real-time observability across your entire fleet.

Open Dashboard
$ curl -sSf getbuild.ing | sh click to copy
Mac mini
# refactor-auth
# add-redis-cache
# fix-ci-pipeline
# update-deps
dev-server
cloud-gpu
Z
New Session
refactor-auth
# refactor-auth
# add-redis-cache
# fix-ci-pipeline
# update-deps
Chat
Planning
Files
Chat
Planning
Files
Z
You2:30 PM
Refactor the auth middleware. Extract JWT verification into its own module and add refresh token rotation.
✓✓ Read
C
Claude2:30 PM
I'll extract JWT verification into a standalone module:
export async function verifyToken( token: string, config: AuthConfig ): Promise<JWTPayload> { const { payload } = await jwtVerify( token, config.secret ); return payload as JWTPayload; }
Z
You2:32 PM
Use Redis for the token store.
✓✓ Read
C
Claude2:32 PM
Switching to Redis with composable middleware chain. Running tests now.
Z
You1:15 PM
Add a Redis cache layer for the API. Cache GET responses with a 60s TTL, bust on writes.
✓✓ Read
C
Claude1:15 PM
Adding cache middleware with key derivation from route + query params. I'll use a write-through invalidation pattern so mutations automatically bust relevant cache entries.
C
Claude1:18 PM
Cache layer is wired up. All 23 tests passing, avg response time dropped from 140ms to 8ms on cached routes.
Z
You11:45 AM
CI is failing on the lint step. Can you figure out what's going on and fix it?
✓✓ Read
C
Claude11:45 AM
Found it — the ESLint config was referencing a removed plugin. Fixed the config and pinned the dependency. Pipeline is green now.
Z
You10:00 AM
Run a full dependency update. Major versions are fine, just make sure tests still pass.
✓✓ Read
C
Claude10:02 AM
Bumped 14 packages including Next.js 14 → 15 and TypeScript 5.3 → 5.6. Had to update two type imports that changed. All 89 tests passing.
Message...
Plans
Extract JWT verification module
Ready · assigned to refactor-auth
Add rate limiting middleware
In progress · 3 of 5 tasks done
Migrate session store to Redis
Ready · unassigned
Add CORS configuration
Backlog
Write API documentation
Backlog
Extract JWT verification module
Ready · assigned to refactor-auth
  • Create auth/jwt.ts with verify & refresh
  • Add Redis token store adapter
  • Update middleware to use new module
  • Add refresh token rotation tests
Description
Extract all JWT verification logic from the auth middleware into a standalone module. Add refresh token rotation with Redis-backed token store for invalidation tracking.
Files
src/
auth/
jwt.tsA
refresh.tsA
middleware/
auth.tsM
rate-limit.tsM
index.ts
package.json
tsconfig.json
src/auth/jwt.ts Added
1import { jwtVerify, SignJWT } from 'jose';
2import { redis } from '../store';
3
4export async function verifyToken(
5 token: string,
6 config: AuthConfig
7) {
8 const { payload } = await jwtVerify(
9 token, config.secret
10 );
11 return payload as JWTPayload;
12}
13
14export async function rotateRefresh(
15 oldToken: string,
16 config: AuthConfig
17) {
18 await redis.set(
19 `revoked:${oldToken}`, '1'
20 );
14m 32s
Tokens 12.4k / 128k
Tests 47 pass / 2 fail
Files 8 modified
Git +247 -89
Warnings 3
Model opus-4
Capabilities

Everything you need to coordinate agents at scale

Agent chat

Direct communication with any agent on any device. Send instructions, review code, and iterate in real time with full message history.

Project planning

Full issue tracker with priorities, assignees, checklists, and activity feeds. Agents update their own progress as they work.

File browser

Browse agent workspaces with a full file tree, inline diffs, and version control integration. See exactly what changed and why.

Complications

Always-visible status cards for git, CI/CD, tests, tokens, and model info. Per-agent context at a glance without switching views.

Local first

Your data stays on your devices. No cloud dependency for core functionality. Works offline, syncs when connected. You own everything.

E2E encrypted

Every message, file, and command is end-to-end encrypted. Not even we can read your data. Zero-knowledge architecture throughout.

Observability

Know everything.
Always.

Complications are always-visible status cards that give you instant context about each agent's work. No digging through logs or switching tabs.

Each agent surfaces the metrics that matter for its task — git status, test results, CI/CD pipelines, model info, token usage, and more.

  • Git status with line-level diffs
  • CI/CD pipeline status in real time
  • Test results as they run
  • Token usage and cost tracking
  • Agents choose their own relevant complications
Model
claude-opus-4-6
Files Changed
+4 added · 3 modified · 1 deleted
Tests
47 passed · 2 skipped · 2 failed
CI/CD
Pipeline passing · Build #142
Tokens
42,847 in · 8,291 out · ~$1.24

End-to-end encrypted.
Zero compromises.

Every message, file transfer, and command between you and your agents is encrypted end-to-end. Your code never touches our servers in plaintext.

Zero-knowledge architecture
Local key management
Open source encryption layer
Auditable by design
Getting started

Up and running in minutes

1

Install

One command. Works on macOS, Linux, and WSL. No Docker, no cloud accounts.

$ curl -sSf getbuild.ing | sh
2

Configure device

A guided TUI walks you through setup — name your device, point it at projects, Claude Code, and git credentials.

device name projects claude binary git creds
3

Create agents

Open the web UI and spin up as many agents as you need. Assign tasks, track progress, and watch them work — all from one dashboard.

Start building
with your fleet

Sign in to access the dashboard and start orchestrating agents across your devices.

Open Dashboard GitHub