Debugging

This guide reflects the current stack and route surface.

Container and Service Logs

docker-compose logs -f api
docker-compose logs -f frontend
docker-compose logs -f postgres
docker-compose logs -f redis

API Health Checks

curl http://localhost:8000/
curl http://localhost:8000/health
curl http://localhost:8000/ready

Use /ready when you want to know whether the database is actually available.

Inspect Agents and Deployments

curl http://localhost:8000/agents
curl http://localhost:8000/deployments
curl http://localhost:8000/agents/YOUR_AGENT_ID
curl http://localhost:8000/agents/YOUR_AGENT_ID/logs?limit=50
curl http://localhost:8000/agents/YOUR_AGENT_ID/metrics?limit=50

Auth Debugging

Register and log in again if you want to validate the auth flow end to end:

Database Checks

If the API is degraded, compare the running DB host to your .env DATABASE_URL.

CLI Debugging

If a CLI command fails unexpectedly, compare it against the route implementations in:

  • cli/commands/agents.py

  • cli/commands/deploy.py

  • src/api/routes/

Frontend Checks

Use npm run test:app for the current app-level Jest coverage under tests/unit/. Do not rely on ad hoc next lint --file ... commands here; the repo's trusted baseline is scripts/test.sh plus targeted unit or Playwright runs.

Playwright Note

Current Playwright smoke coverage runs locally via the checked-in config. Use npx playwright test --list first to confirm discovery and then run the smallest matching spec or grep target.

Trusted Validation Baseline

That script is the current repo-native validation baseline and now includes:

  • Python lint and format checks

  • Python compile checks

  • full API pytest suite

  • OpenAPI type generation

  • app-level frontend unit tests

  • production build verification

  • targeted Playwright smoke coverage

Last updated