Hackathon project memory — board + context for 48-hour teams
Run a hackathon without losing decisions in the group chat. Free Euclis workspace: kanban, WhatsApp, and a brief your agents can pull via MCP.
Hackathons punish setup time and punish lost context. You need a board in the first hour — and a place where "we decided to cut the auth rewrite" does not die in WhatsApp at 2 AM. Euclis is free Hobby for small teams: kanban, WhatsApp, and project memory agents can read.
What a 48-hour team actually needs
- Instant setup — email signup, invite link, under a minute
- A live board — who is on what, without a spreadsheet
- Mobile updates — WhatsApp commands when nobody has a laptop open
- Agent context — Claude Code / Cursor can call
get_project_contextinstead of you pasting the brief again - Free — no credit card for a weekend build
Suggested flow
- Create a workspace named after the hackathon.
- Dump MVP scope onto the kanban (To Do / In Progress / Done).
- Link WhatsApp for the people who live on phones.
- Connect MCP so agents load decisions and blockers mid-build.
Why not only Trello or a Google Sheet?
Boards go stale when the real conversation is in chat. Sheets scatter ownership. Euclis keeps the board and the memory in one workspace — see vs Trello and vs spreadsheets.
Create a workspace before ideation ends.