agent harness

AI Community

Skill notes

Step 1: Discover Your Agent ID

Your agent ID determines all your ports and resources. Find it by checking for the generated environment file: This will show something like .env.agent.1 — the number is your agent ID. Alternative: Check which PM2 processes are running:

Step 2: Know Your Ports

Once you have your agent ID, your ports are deterministic: Service · Formula · Agent 1 · Agent 2 · Agent 3 Frontend (Vite) · 3000 + (ID × 10) · 3010 · 3020 · 3030 Backend API · 8000 + (ID × 10) · 8010 · 8020 · 8030 Node Debugger · 9200 + (ID × 10) · 9210 · 9220 · 9230

Step 3: Use the CLI

All stack management goes through agent-cli.sh:

Step 4: Verification Workflow

Run verification after every code change: Output is JSON to stdout: Stages run in order, stopping on first failure: typecheck — TypeScript for common, backend, frontend (parallel) lint — ESLint for common, backend, frontend (parallel)

Making code changes

Edit files as needed If you changed packages/common/, the TypeScript watcher auto-rebuilds If you changed packages/backend/, restart the API: Run verification:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@lightdash · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Node.js · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Discover Your Agent ID

Your agent ID determines all your ports and resources. Find it by checking for the generated environment file: This will show something like `.env.agent.1` — the number is your agent ID. Alternative: Check which PM2 processes are running:

02
Step 2: Know Your Ports

Once you have your agent ID, your ports are deterministic: Service · Formula · Agent 1 · Agent 2 · Agent 3 Frontend (Vite) · 3000 + (ID × 10) · 3010 · 3020 · 3030 Backend API · 8000 + (ID × 10) · 8010 · 8020 · 8030 Node Debugger · 9200 + (ID × 10) · 9210 · 9220 · 9230

03
Step 3: Use the CLI

All stack management goes through `agent-cli.sh`:

04
Step 4: Verification Workflow

Run verification after every code change: Output is JSON to stdout: Stages run in order, stopping on first failure: typecheck — TypeScript for common, backend, frontend (parallel) lint — ESLint for common, backend, frontend (parallel)

05
Step 5: Test Login Credentials

Step 5: Test Login Credentials

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.