A desktop coding agent with free access to frontier models.
TypeScript
Routes
This folder groups Den API endpoints by product surface instead of keeping one large router file.
Layout
auth/: Better Auth mount and desktop handoff routesme/: current-user routes that describe the signed-in user and their org accessorg/: organization routes split into focused files by concernadmin/: admin-only operational endpointsversion/: public app version metadata for desktop update checksworkers/: worker lifecycle, runtime, billing, and heartbeat routes
Conventions
- Each route area exports a single
register...Routes()function from itsindex.ts - Request validation should use Hono Zod validators from
src/middleware/index.ts - Shared auth/org/team context should come from
src/middleware/index.ts, not from ad hoc request parsing - Routes are deny-by-default in CI: new routes must use shared auth middleware or be added to
test/route-guard-policy.test.tswith a narrow reason - New route areas should get their own folder plus a local
README.md
Why this exists
Agents often need to change one endpoint family quickly. Keeping route areas isolated makes it easier to understand ownership and avoid accidental cross-surface regressions.