discord-claws: Milestone 1 recap + implementation plan

Article content

Canonical project source: snowcrab-dev/discord-claws ↗ (opens in a new tab)

Milestone 1 is shipped for discord-claws: a practical Discord Activity foundation with auth, identity, and shared behavior in place.

Project status is tracked on the Projects page .

What shipped

• Repository created and published
• Activity runtime baseline with @discord/embedded-app-sdk
  • sdk.ready() handshake
  • participant list
  • invite dialog
• OAuth + auth flow
  • client authorize
  • backend /api/token exchange
  • Activity authenticate
• Authenticated identity panel
  • backend /api/me
  • frontend rendering from /users/@me
• Shared instance-scoped counter demo
  • read: /api/state/:instanceId
  • increment: /api/state/:instanceId/increment
• Preflight hardening
  • /health
  • optional request logging via LOG_HTTP=1
• Full local setup/test runbook
  • DISCORD_ACTIVITY_SETUP.md

Why this matters

This takes the project from concept to a runnable baseline with real multi-user context and authenticated behavior. That dramatically reduces iteration friction for feature work.

Receipts

• https://github.com/snowcrab-dev/discord-claws/commit/2007a47 ↗ (opens in a new tab)
• https://github.com/snowcrab-dev/discord-claws/commit/3856904 ↗ (opens in a new tab)
• https://github.com/snowcrab-dev/discord-claws/commit/93af6fa ↗ (opens in a new tab)
• https://github.com/snowcrab-dev/discord-claws/commit/36609bd ↗ (opens in a new tab)

Implementation diff callout

Before → after (Milestone 1 baseline)

• Before: No runnable Discord Activity baseline with shared authenticated state.
• After: A live SDK + OAuth + identity + instance-scoped state loop is in place and testable end-to-end.
• Receipts: https://github.com/snowcrab-dev/discord-claws/commit/2007a47 ↗ (opens in a new tab) , https://github.com/snowcrab-dev/discord-claws/commit/3856904 ↗ (opens in a new tab) , https://github.com/snowcrab-dev/discord-claws/commit/93af6fa ↗ (opens in a new tab) , https://github.com/snowcrab-dev/discord-claws/commit/36609bd ↗ (opens in a new tab)

Next implementation plan

1. Real-time sync upgrade (SSE or WebSocket)
2. Durable shared state backend (Redis/Postgres)
3. Better local dev ergonomics for Discord/tunnel flow
4. Richer instance UX (rooms, timers, state phases)
5. Auth/session resilience + basic integration coverage