Ogment AI - Your AI coworker, in Slack. Just tag @O.
by•
@O is the ultimate AI coworker that lives natively in Slack.
Tag @O like a colleague, to ask anything or delegate daily tasks in plain English. It connects to 1,000+ tools your business runs on, does work while you sleep, and shares memory and skills across your whole team right in Slack, on any model you choose, including your own.
One-click install, and everyone is AI-enabled in under 5min, not just your power users. Zero friction, maximum adoption.
Replies
How does pricing actually work if multiple teammates are tagging @O throughout the day — is it per user, per workspace, or based on the volume of tasks it handles?
@O - AI coworker in Slack
@vedatkarabjvvk - it's usage-based, tied to the volume of work @O handles, not per user or per workspace. So multiple teammates tagging it all day doesn't mean seat-by-seat costs, you add the whole team freely and pay for actual tasks done. And since it's model-agnostic, you've got a real cost lever by pointing it at a cheaper one!
@O - AI coworker in Slack
Sonnet became super efficient and cost efficient!
Love the breezy integration, making me to automate time-wasting workflows without me having to think twice about it (for me it's scheduling + note aggregation / tracking)!
@O - AI coworker in Slack
@ferdinand_legros love it, thanks Ferdi. Good to see you here!
Fellow.ai
congrats on the launch! looking forward to checking this out
@O - AI coworker in Slack
@manuelabarcenas Thank you, Manuela. Looking forward to having you on the platform.
The shares-memory-and-skills-across-your-whole-team part plus running automations while you sleep is the combination I would want to pin down before rolling it out. When @O touches one of those 1,000+ tools, is the connection scoped per-user so it acts with my permissions, or is it one workspace-level token everyone shares? And the shared team memory: does that live in your infra, or can I point it at our own store or model like the including-your-own line suggests?
whats the core differentiator between this and openclaw ?
@O - AI coworker in Slack
@roy_kek Great question - OpenClaw is awesome.
The core difference is who it's built for. OpenClaw is a self-hosted, single-user personal assistant - you run the gateway yourself, wire it up in the terminal, manage tokens and updates. Amazing if you're technical and want something local and fully yours.
@O is the opposite bet: a managed product built for whole teams. One-click install, no infrastructure to run, connectors approved once by IT, and SOC 2 / GDPR handled for you. Every employee gets their own agent, memory and skills are shared across the org, and you get adoption analytics to see who's actually using it.
So: OpenClaw = personal assistant for one technical builder. @O = governed AI coworker for an entire team, zero ops. Different jobs.
How does Ogment decide when an AI agent should act autonomously versus asking for human approval?
Prefactor
How much is the pricing?
@O - AI coworker in Slack
@ethan_lee8 It's credit-based and starts at $50/month. One workspace plan, unlimited Slack users - so the whole team can use it, and you only pay for actual usage rather than per seat.
"1,000+ tools" and "runs automations while you sleep" is a lot of standing permission to hand an agent that anyone on the team can just @ tag. what does the actual access model look like - does @O inherit whatever permissions the person tagging it has, or is there a separate admin-approved scope per tool/integration?
This looks great! I will definitely give it a test drive.
Do you think it will also work for multiplayer vibe coding?
@O - AI coworker in Slack
@tleyden Thanks - hope you like it when you take it for a spin! 🙌
Honest answer: @O isn't really built for vibe coding. It shines at delegating tasks across your tools (CRM, docs, email, data) right from Slack, not at pair-programming in a shared editor. For multiplayer vibe coding you'd want something like Cursor.
That said, there's an overlap worth flagging: @O is great for the stuff around the code. Tag it in a channel to triage issues, summarize a PR thread, kick off a deploy, update Linear, or pull context from your tools while the team codes. So less "coding together," more "the teammate handling everything that isn't the code."
@O @teoborschberg Makes sense! Slack seems like the right environment to interact with an ai virtual assistant. I will definitely give it a spin!