Wack Hacker

AI-powered Discord bot for Purdue Hackers. Wack Hacker coordinates specialized subagents to manage many of our resources from Discord threads.

• Talk to your tools. @mention the bot in any thread to read and act on the services we use without leaving Discord.
• Multi-turn memory. Conversations persist across messages, restarts, and deploys, so you can come back to a thread hours later and pick up where you left off.
• Full Discord surface. First-class support for gateway events, slash commands, message components, and cron jobs — write a handler, register it, ship it.
• Scheduling. Ask the bot to remind you, post on a schedule, or run a task once at a specific time. Recurring jobs survive redeploys.
• Role-aware capabilities. Public users get safe read tools; organizers unlock writes across our stack; admins get destructive operations. Permissions follow your Discord role.

Domains

Subagents are grouped by what they touch, not by how they're wired up. Organizer role unlocks everything except delegate_code, which is admin-only.

Communication & knowledge

• Discord — channels, threads, messages, members, roles, emojis, webhooks, scheduled events.
• Notion — read and write pages, query and update databases, post and resolve comments.
• Documentation — search and quote from ask.purduehackers.com for questions grounded in Purdue Hackers' own docs.

Engineering

• GitHub — repositories, issues, PRs, file contents, workflows, deployments, packages, projects, secrets, org settings.
• Linear — issues, views, projects, initiatives, updates, documents, reminders, customer requests, users.
• Sentry — error monitoring, events, stack traces, releases, alerts.
• Vercel — projects, deployments, runtime logs, env vars, domains, edge config, feature flags, rolling releases, marketplace integrations (Turso/Upstash/Neon), sandboxes, firewall.
• Figma — files, components, styles, design tokens, variables, comments, dev resources.
• Code (admin-only) — autonomous coding agent that runs inside a Vercel Sandbox against a purduehackers/* repo, makes changes on a feature branch, runs checks, and opens a PR.

Operations

• Finance — read-only Hack Club Bank lookups: balances, transactions, donations, invoices, card spend.
• Shopping — Amazon product search and a shared virtual cart/wishlist.
• Sales — Notion CRM (Companies/Contacts/Deals), Hunter.io email finder, Resend outreach send/tracking.
• CMS — Payload CMS at cms.purduehackers.com: events, RSVPs, hack-night sessions, email campaigns, media, microgrants, shelter projects, users.

Built on Next.js App Router + Hono (via hono/vercel), AI SDK v6, and Workflow DevKit. Deployed on Vercel with Fluid Compute.

Setup

Prerequisites

• Bun >= 1.3.10

Environment

bunx vercel env pull --yes

Env is validated by src/env.ts using @t3-oss/env-core.

Development

bun install
bun dev

Next.js dev server runs at http://localhost:3000. To take traffic you need to either:

• Hit GET /api/discord/gateway to spin up the discord.js gateway listener (it will publish packets to the discord-events queue, consumed by /api/discord/events), or
• Point Discord's Interactions Endpoint URL at {BASE_URL}/api/discord/interactions for slash commands and component callbacks.

Scripts

Command	Description
bun dev	Start Next.js dev server
bun run build	Compile skills → next build → register slash commands
bun run typecheck	tsc --noEmit
bun run lint	oxlint --type-aware
bun run format	oxfmt
bun run test	Unit tests (vitest)
bun run test:integration	Integration tests
bun run test:coverage	Coverage report (90% threshold)
bun run validate	typecheck && lint && test
bun run knip	Unused-code report

Documentation

Reference docs for the codebase live in docs/:

• Architecture — system shape, request flow, agent hierarchy, skill system.
• Discord layer — gateway, interactions, EventRouter, queue consumer, handler patterns.
• Agents — orchestrator, delegate subagents, AgentContext, streaming, role gating.
• Skills — SKILL.md format, registry, progressive disclosure, admin gating, adding skills.
• Workflows & scheduling — chatWorkflow, taskWorkflow, hooks, recurring jobs.
• Deployment — vercel.ts, queue triggers, environment variables, build pipeline.
• Testing — Vitest, integration suite, coverage thresholds.