Launching today

PromptQL
Multiplayer AI that replaces Slack
321 followers
Multiplayer AI that replaces Slack
321 followers
Stop splitting team knowledge between Slack and everyone's private AI chats. PromptQL is multiplayer AI for teams: think Claude or ChatGPT in shared threads. Tag teammates to review, correct, and refine answers without losing the reasoning. Connect databases, SaaS apps, coding agents, and events. PromptQL captures tribal knowledge and suggests shared-brain updates so context compounds. Scopes and multi-user permissions keep the right context accessible to the right people.










the 'tag teammates to review/correct without losing the reasoning' part is the actual hard problem, most team-AI tools just dump a shared chat log and call it collaboration. when someone corrects an answer mid-thread, does that correction get folded back into the shared-brain context for future questions or does it just live as a one-off reply in that thread?
PromptQL
@omri_ben_shoham1 Yes, it gets folded back in. Everything durable worth learning in a thread is actively learnt and it is also shown to the user for review before "committing" it to the shared context.
You can see the entire change log of the shared context and tie it back to the originating threads as well.
the scopes/permissions part is the sharp edge - if someone corrects an answer in a restricted-scope thread, does that correction ever bleed into the shared-brain for people outside that scope, or does it stay siloed to who saw the original thread?
PromptQL
Locofy.ai
interesting idea. what made you take on slack?
PromptQL
@honeymittal It was accidental! We started out building AI that'd be accurate when connected to company data.. and it soon became obvious that the missing layer was shared context. As we started to build out the system that would capture shared context- aka multiplayer AI, we suddenly realised we're built an AI native slack!
PromptQL
Fable Flight
cool video, shared context, skills and existing workflows to hyper automate development. dosent this reduce hiring needs
PromptQL
Fable Flight
@tanmaig isnt that waht codex is abt. is this more buisness ops?
PromptQL
PromptQL
I never thought we could replace Slack completely, but when we did and started doing almost all work in PromptQL I realized the true power that a "native AI" experience can bring in an enterprise.
My usual flow when I am stuck is ask PromptQL, and it just knows - because someone else had figured it out earlier and PromptQL had learned it. Everything from "who has office keys" to "how can I access to the latest open-weight model in my local dev" - it JUST knows. Apart from asking questions, I ask it to do things, whenever I find a small product issue - I don't just raise the issue with the engineering team, I ask PromptQL to fix -> show me preview -> inform appropriate team/people for an approval -> deploy.
PromptQL
@tiru_selvan it's kind of cool how it makes you feel closer to everyone else in the team. even though you're using AI. Because you're like: 'wait, how did you know, oh because X taught it, so cool'.
The "shared-brain updates so context compounds" framing is different from other team AI tools. One thing I'd be curious about—when corrections and learning flow back into the context, how do you prevent authoritative corrections from overweighting domain expertise that was already in the system? Like, if someone corrects a nuance mid-thread, does it need peer review before it locks in, or is the cost of outdated shared context higher than the cost of wrong-but-quick updates?
What is nuts about working with PromptQL is how easy is to say:
“Is this thing a problem? Show me data”
“Right, what should we do to fix it”
“Yeah that looks like a good fix, let’s iterate a bit and then deploy it”
“Monitor the problem data every day and let’s check we fixed the problem”
When “doing things” is cheap, making sure you’re not doing useless things is key, and that’s so easy for me now.
PromptQL
@dan_harvey and that's also the reason it feels like the rate of changes to the wiki (shared context) seems to be steadily increasing. which i found very surprising. I would have expected that the rate settles down to a small steady rate once all the shared context has been taught.
but exactly to your point, why would I stop after teaching it one thing. I'll move on to the next thing. done right i think it's like a continuous acceleration. too weird to comprehend what that means....
PromptQL
@dan_harvey @tanmaig it's kind of crazy that I still have aha moments every other day even though I live in the product!