Task Workspace: task management right inside Discord
I built a task management tool with two-way sync to Discord and Telegram. Here's why, and how it works.
Every small team starts managing work in Discord or Telegram. It’s fast, it’s handy, everyone is already there. But after a few weeks, messages scroll away, tasks get lost, and nobody remembers the deadlines.
The usual fix is to move to Jira, Trello or Linear. The catch: the team still chats on Discord. Now everyone has to jump back and forth between two apps. The adoption rate is close to zero.
The idea
Instead of making the team leave Discord, I brought task management into Discord.
Task Workspace syncs both ways, in real time. Create a task on the web and it shows up in the Discord channel as a rich embed. Reply on Discord and it becomes a comment on the web. Type /done TASK-42 and the task updates in both places. Zero friction.
How it works
- Create a Workspace for the team and invite members by email; the system generates an invite link with role assignment
- Connect the Discord bot or Telegram bot: OAuth flow, channel binding, permission sync
- Use slash commands (
/create,/list,/done,/assign): full CRUD from chat - A web dashboard for the bird’s-eye view: Kanban, filters, analytics. Every change syncs instantly.
Behind the scenes
- Bi-directional sync engine: event-driven architecture. Every action on the web emits an event, and the Discord/Telegram adapter transforms and pushes it. The other way round, every bot command is parsed, validated, executed, then emitted back to the web over WebSocket
- Loop prevention: the classic problem of two-way sync. Every message carries an
externalProviderflag. The adapter checks the flag before forwarding; if the message came from itself, it skips it. Simple, but bulletproof. - Atomic auto-numbering: each workspace has its own counter in Redis.
INCR workspace:{id}:counterreturns the next number in O(1), thread-safe, zero collisions. Task IDs look likeTASK-1,TASK-2… - Custom status machine: each workspace defines its own flow. Default: TODO → IN_PROGRESS → TESTING → DONE. Teams can add, remove or reorder statuses to fit their workflow.
- Presigned upload: files never pass through the server. The client asks Cloudflare R2 for a presigned URL, uploads straight from the browser, then saves the reference. The server never touches file content, which saves bandwidth and latency.
Tech stack deep dive
Frontend monolith: Next.js 16 with the App Router + React 19 concurrent features. The UI layer is built on Radix UI primitives, wrapped with shadcn/ui for consistency. Forms use React Hook Form + Zod schema validation: type-safe from the form to the API call.
Backend DDD: Express.js structured by Domain-Driven Design. Each domain (Task, Workspace, Comment, Integration) is an independent module with a Controller → Service → Repository pattern. TSOA auto-generates OpenAPI specs from TypeScript decorators, so the API docs always match the code.
Data layer: PostgreSQL 16 for relational data (tasks, users, workspaces) with Prisma ORM type-safe queries. Redis 7 for caching, rate limiting, pub/sub events and atomic counters. Cloudflare R2 for file storage: S3-compatible, with zero egress fees.
Auth pipeline: JWT access token (15 min) + refresh token rotation. Firebase Admin SDK handles the Google OAuth flow. Email OTP verification at registration. Stateless auth, so it scales horizontally.
Try it at workspace.thomas-labs.com.
Related posts
VieChoice English: learn vocabulary with spaced repetition + AI
A free vocabulary learning platform built on spaced repetition and AI. This is the story behind the product.
2026-04-24xcluster: a control plane for your homelab
I built a platform to manage my whole homelab from the browser: SSH terminal, Docker, Wake-on-LAN, monitoring. Written in Go.