Mantle Chat - Collaboration platform where teams work with AI together
by•
Mantle Chat helps teams boost productivity and adopt AI faster by bringing real-time messaging, AI model chats, autonomous agents, and tool integrations into one shared workspace. Communicate in Discord/Slack-style channels, mention AI agents and models (GPT, Claude, Gemini, Grok, Deepseek) with @ whenever you need help directly in conversations with teammates, build agents, run autonomous tasks together, and connect 30+ tools (Notion, Linear, Gmail and more) your team already uses.
Replies
ProdShort
I’ve been jumping between Claude and ChatGPT tabs for months depending on what I’m working on. Never really found a smooth way to keep both in one workflow.
Mantle looks interesting for that. Curious to see if having one workspace actually solves it.
Mantle Chat
@amraniyasser Thank you, feel free to reach out if you need more info.
One underrated benefit here is institutional memory . Shared AI conversations are way more valuable than knowledge trapped in private chats.
Mantle Chat
@gabriel_brooks1 Thanks you! Definitely, private AI chats are useful for individual productivity, but shared AI threads turn that productivity into team knowledge.
Does Mantle keep a persistent shared context across sessions — so the AI understands decisions the team made in previous conversations — or does each new session start fresh? That long-term memory layer seems like the thing that would make it genuinely more useful than just adding AI to a Slack channel.
Mantle Chat
@sunnyallan Thanks for your question!
Mantle Chat doesn’t treat every new session as completely fresh, if you add context to the workspace knowledge base.
Teams can add shared files, instructions, and context at the workspace level, and agents can use that across conversations. We also support agent-level knowledge bases, so each agent can have its own specialized context.
We’re also working on the desktop app and local file access, so the context layer can go beyond just what was said in a single channel or thread.
Love the shift from isolated chat to collaborative, event-driven agent workflows. When your agents are running in 'Flows' and interacting autonomously with multiple external APIs like Stripe or GitHub, how does the system handle state persistence and error recovery? If an API rate-limits the agent halfway through a scheduled task, I'm curious if the agent can dynamically adapt and retry, or if it hard-fails back to a human
Mantle Chat
@rugved_chavan Thank you for your question!
State persistence is fully Postgres-backed. Every agent run is a database row with a clear status lifecycle: pending → running → success/failed. We use unique partial indexes to guarantee only one active run per trigger, and idempotency keys to prevent duplicate executions. For task chains (A triggers B triggers C), each run tracks its parent and depth, with a hard cap at 10 levels to prevent runaway cascades.
For error recovery — the system follows a fail-and-notify model. If an API rate-limits or errors mid-execution, the run fails with a 5-minute timeout, the error gets recorded, billing reservations are cancelled, and the trigger creator gets a real-time notification. We intentionally chose this over silent auto-retry — when agents interact with real external APIs, retrying blindly risks duplicate side effects (double-charging a customer, posting duplicate comments).
On the resilience side: a background worker periodically detects stuck runs and marks them as failed, advisory locks prevent concurrent scheduling conflicts across replicas, and triggers auto-disable themselves when backing credentials (Stripe OAuth, Linear tokens) get revoked. So the system degrades gracefully rather than failing noisily.
Right now we're paying for 4 different AI tools across a 6 person team. No shared history, no shared context, and the bill keeps growing. This looks like the first real alternative. Want to give it a proper test.
Mantle Chat
@andrzej_zarod Thanks for your comment! This is exactly what we’re trying to solve: one shared AI workspace for the whole team, with shared context and history.
Feel free to try it out, we have a free tier for teams.
CatDoes
Congrats on the launch! This looks really promising! Been looking for something like this! @katja_danilina
Mantle Chat
@nafis_amiri Thank you very much for your support!❤️
Triforce Todos
Mantle Chat
@abod_rehman Thank you!
Congratulations. And happy product launch. @katja_danilina
Mantle Chat
Does Mantle keep a persistent shared context across sessions — so the AI understands decisions the team made in previous conversations — or does each new session start fresh? That long-term memory layer feels like the key differentiator for async teams.
Mantle Chat
@sunnyallan I think this comment is duplicated, I already replied here: https://www.producthunt.com/products/mantle-chat?comment=5382624