Authentication (Better Auth)

SkillSecurity

Lets your agent handle sign-in and sign-up flows, sessions, OAuth, and magic links.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Authentication (Better Auth) skill

About this capability

Sessions, sign-in/sign-up flows, OAuth, magic links, or organization context on the session.

What this skill tells your AI

The instructions your AI receives, as published by latitude-dev/latitude-llm in .agents/skills/authentication/SKILL.md and read by ahel’s review.

When to use: Sessions, sign-in/sign-up flows, OAuth, magic links, or organization context on the session.

@platform/db-postgres exposes createBetterAuth() in packages/platform/db-postgres/src/create-better-auth.ts, wiring better-auth with the Drizzle adapter against the shared Postgres client.
Sessions: auth.api.getSession({ headers }) → { user, session } with typed fields.
User includes id, email, name — use those fields directly (no assertions).

Session helpers: apps/web/src/domains/sessions/session.functions.ts (getSession, ensureSession, etc.).
Organization context is added via the customSession plugin (multi-tenant product behavior).

Auth intent flows (login/signup completion) use use-cases from @domain/auth composed with Postgres repositories — keep policy in domain, wiring in apps.

For HTTP boundary rules (who may call what), see architecture-boundaries.

Advanced