@O - AI coworker in Slack
Your AI coworker, in Slack. Just tag @O.
769 followers
Your AI coworker, in Slack. Just tag @O.
769 followers
@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, runs automations while you sleep, and shares memory and skills across your whole team right in Slack. One-click install, everyone AI-enabled in under 5min. Zero friction, maximum adoption.
This is the 2nd launch from @O - AI coworker in Slack. View more
Ogment AI
Launching today
@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.
Free Options
Launch Team / Built With
how does pricing scale when a whole team starts tagging @o constantly throughout the day, does it balloon fast?
@O - AI coworker in Slack
@glerioqv - honestly, with Opus 4.8 it could add up fast at high volume. But Sonnet just landed about 3x cheaper with basically the same performance for this kind of work, so the math changed a lot, we're getting to genuinely competitive pricing even at scale now. And since you can point @O at different models, you've got a real lever to tune cost vs power per use case rather than paying top-tier for everything.
how does the shared memory actually work across teammates, like is there a way to keep some context private to just me vs stuff that everyone in the channel can see
@O - AI coworker in Slack
@aryaxrhm yep, exactly that split by design. Two layers: personal memory that's private to you (learned from your own tasks, stays yours) and an org-level layer an admin shares team-wide. So your own context doesn't leak to teammates, and the shared stuff is there on purpose, not by default.
how does the memory actually get shared across teammates without it getting weird when someone else pulls up context from a thread i was part of
@O - AI coworker in Slack
@samitcmo good q, and yeah the "weird" part is exactly what we designed around. Your personal memory stays yours, it doesn't get pulled into someone else's agent just because you shared a thread. What's shared team-wide lives in a separate org layer an admin curates, so context spreads on purpose, not by someone accidentally surfacing your stuff.
Curious how the shared memory actually works between teammates, does anything I share with @O stay private to me or does the whole team see the context it picks up?
@O - AI coworker in Slack
@aytenklkesfmuc - Stays private to you by default. Two layers: personal memory that's yours alone (learned from your own tasks) and an org-level layer an admin deliberately shares team-wide. So what you tell @O doesn't just spill to the whole team, the shared stuff is there on purpose :)
How does the shared memory actually work between teammates — is there a way to keep some context private to just me, or does everyone see everything I ask @O?
@O - AI coworker in Slack
@rzakalpcaj9w - Yep, private-to-you is the default. Two layers: personal memory that's yours alone (learned from your own tasks) and an org-level layer an admin shares team-wide on purpose. So everyone does not see everything you ask @O, your stuff stays yours, and the shared context is deliberate.
How does the memory sharing actually work between teammates, like can it see what others have asked or does each person keep their own separate context?
@O - AI coworker in Slack
@hazal395430 Ha, this is easily the most-asked question of the launch, clearly the thing everyone wants to know, and we love it 🙂 Each person keeps their own separate context by default, so your agent can't just see what a teammate asked. On top of that there's an org-level layer an admin shares team-wide on purpose, for stuff everyone should have. So personal stays personal, shared is deliberate!
How does the shared memory actually work between teammates, like can I keep certain context private to just me or does @O sync everything across the whole workspace?
@O - AI coworker in Slack
@alisennecl99142 You can absolutely keep context private to just you, that's the default. @O doesn't sync everything across the workspace. Two layers: personal memory that's yours alone (learned from your own tasks) and an org-level layer an admin shares team-wide on purpose. So your stuff stays yours, shared context is deliberate.