Euclis vs TaskRio — project memory vs WhatsApp group bot
TaskRio runs inside WhatsApp groups. Euclis uses a private 1:1 bot plus web memory, Dreaming, and MCP for agents — same workspace, different model.
Both products meet teams in WhatsApp. TaskRio is a group bot. Euclis is a private assistant plus a full workspace with project memory for humans and coding agents.
TaskRio's group model
You invite @TaskRio into a WhatsApp group. The bot stays quiet until @mentioned (or someone replies to its task cards). Groups often need manual admin approval before automation works. Task cards and standup summaries can appear in the thread.
Euclis's model
Each teammate messages Euclis in a 1:1 chat. Updates hit the shared board and feed workspace memory. Agents pull the same brief via MCP. Your group chat is not a bot channel.
Side-by-side
| Feature | Euclis | TaskRio |
|---|---|---|
| WhatsApp model | Private 1:1 bot per linked user | Bot inside WhatsApp groups (@mention) |
| Group chat | Stays human — no bot cards in the thread | Task cards and summaries in the group |
| Project memory | Decisions, blockers, Dreaming maintenance | Task-focused; not a memory product |
| AI agents / MCP | Yes — get_project_context and board tools | No |
| Web workspace | Kanban, discussions, whiteboard, assets | Lighter task surface |
| Onboarding | Email signup; link phone when ready | Group invite + admin approval |
| Best for | Teams that want web + agents + optional WhatsApp | Teams whose entire workflow is one WhatsApp group |
When to choose TaskRio
- The whole workflow is one WhatsApp group
- You want task cards visible in the group thread
When to choose Euclis
- You want web kanban + memory + MCP, not group-bot-only
- You prefer private bot chats
- Hackathons / side projects with mixed web and mobile users