Built on Auth0 Token Vault

Your AI Knows Your
Developer Context

Connect GitHub, Calendar, and Slack. Ask your AI assistant anything about your work. Control exactly what it can access.

GitHub

Pull requests, commits, notifications, and review assignments

Google Calendar

Upcoming meetings, scheduling context, and daily schedule

Slack

Unread messages, channel summaries, and team mentions

How It Works

Three steps to AI-powered developer briefings with full control

01

Connect Services

Sign in with Auth0 and connect GitHub, Google Calendar, and Slack. OAuth tokens are stored securely in Auth0 Token Vault.

02

Set Permissions

Control exactly what the AI can access. Grant read-only GitHub access, limit Calendar visibility, or revoke Slack entirely.

03

Ask Anything

“Brief me for standup”, “What PRs need my review?”, “Summarize #engineering”. The AI fetches real data through Token Vault.

Built for Trust

The permission model isn't an afterthought — it's the product

Security Model

OAuth tokens stored in Auth0 Token Vault. Your app never sees raw provider credentials. RFC 8693 token exchange ensures scoped, time-limited access.

User Control

Grant or revoke access per service instantly. The Permission Control Center shows exactly what your AI can and cannot access.

Audit Trail

Every token exchange is logged. See which services the AI accessed, when, and what data it retrieved. Full transparency.

Architecture

User  -->  Auth0 Login  -->  Token Vault stores OAuth tokens
                                |
Next.js App  -->  AI SDK  -->  Claude / Gemini (tool calls)
                                |
Tool: "listPullRequests"  -->  Token Vault exchange  -->  GitHub API
Tool: "getTodaySchedule"  -->  Token Vault exchange  -->  Calendar API
Tool: "getUnreadMessages" -->  Token Vault exchange  -->  Slack API
                                |
Streaming response  -->  Chat UI  +  Audit Log
Next.js 16@auth0/nextjs-auth0 v4@auth0/ai-vercelVercel AI SDKTailwind CSS
Built for the Auth0 “Authorized to Act” Hackathon