Praxos
team messaging with built-in memory
Details
- External ID
- 49380160
- Source
- HN
- Company
- —
- Product
- Praxos
- Website domain
- praxos.ai
- Launched
- Aug. 20, 2026
- Cohort
- —
- Upvotes
- 5
- Upvotes percentile
- 0.12634408602150538
- Tags
- —
- Fetched at
- Sept. 10, 2026, 5:32 a.m.
- Updated at
- Sept. 10, 2026, 5:32 a.m.
Description
Hey HN! What does a regular workflow at a startup look like?Probably like this:> One founder talks to customers> Another founder builds> A customer asks for something. The first founder explains it to the second. The second founder explains it to Claude> Two weeks any one of the founders asks one of the following questions: \* Why are we building it this way? \* What happened here? \* What did we promise ACME we’d do? \* How far along are we on X? > Then you scream on the inside because you have to figure out what happened...Before agents, the person who did one part of the work usually held a mental map. They could share the context with other people. Increasingly, they can’t.Small teams can run far more work in parallel than ever before thanks to AI, but someone now has to connect all that context manually. The reasoning behind one product change might now be scattered across a customer call, two emails, a Slack thread, and four Claude conversations.Praxos is a team messaging app.It has channels, groups and threads like you’d expect. However, places where work happens—Github, harnesses, email, calls—get linked and converted into a living record of your company. This means everyone is always up to date with the latest developments.Agents can join conversations and inherit the same context humans do.Here are examples we’ve seen in production:You talk to a customer. Later, when an engineer or coding agent works on the feature, your conversation and the customer’s information are already in context. A new engineer picks up an existing project. They have immediate access to info about who worked on what part of the code base, the deltas across changes, and a granular view of their conversations with coding agents. There’s no need to interrogate the CTO. Three weeks later, someone asks why the engineer made a certain decision about the feature. Praxos fetches the engineer’s convos, the original feature request and call logs between the founder and the engineer. Then it contextualizes the work.We’re early, but the core product already works and is in use. You get messaging, search, memory and connectors. You can bring your own agents, use ours, or both.A desktop app is going live next week. We’re building native calls and mobile apps, so that all the communications that go into a company’s history can happen on Praxos.If you’re a 2 to 10 person team where one person is spending all day with customers while the rest of the team is shipping with Claude/Codex, we’d love to personally onboard you.Especially if you’ve already caught yourself asking “what did the customer want?” or “what’s going on with X?” last week.The first 10 teams to sign up get Praxos for free for 6 months.Email [email protected] to get started!
Enrichment
- Theme
- AI agent frameworks and developer tools
- Vertical
- Horizontal
- Function
- Communication
- Audience
- B2B
- AI stance
- AI feature
- Project type
- Commercial product
- Normalized one-liner
- team messaging with memory
- Manually corrected
- False
Could you build this?
Yes The core product is a chat application with a vector database or retrieval pipeline attached to conversation history to answer user queries using context.
Discussion
2 comments analyzed.
Competitors mentioned: Third-party spam infrastructure providers, WhatsApp Business API, Third-party customer support bots
Concerns raised: iMessage does not allow bots, WhatsApp does not allow bots
Competitors
Other products that read as similar to this one — 142 launches clear the similarity bar, closest 8 shown.
Attention rank: #119 of 143 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 295 days after the earliest competitor.
- AMA2, messenger built for AI agent · hn · 2026-06-30 · 5 upvotes · similarity 0.45
- Praxos Update: iMessage and SMS Actions · hn · 2025-10-29 · 5 upvotes · similarity 0.44
- AgentCouch · hn · 2026-07-30 · 7 upvotes · similarity 0.43
- Parley · hn · 2026-08-11 · 9 upvotes · similarity 0.43
- ContextVault · hn · 2026-07-13 · 12 upvotes · similarity 0.40
- 127 PRs to Prod this wknd with 18 AI agents: metaswarm. MIT licensed · hn · 2026-02-03 · 5 upvotes · similarity 0.40
- CoreMem · hn · 2026-05-22 · 5 upvotes · similarity 0.39
- I built a tool to create AI agents that live in iMessage · hn · 2026-01-04 · 54 upvotes · similarity 0.39