What are you building with Statewave?

[smaramwbc]

We want to learn from the people building real things on top of Statewave (or seriously evaluating it). The patterns that show up here are the strongest signal we have for what to ship next.

Drop a comment with whatever you're comfortable sharing. You don't need to fill in everything — even partial answers are useful.

Tell us about

The agent or app

• What kind of agent or product is it? (support, coding, workspace, account, voice, research, infra, custom)
• Who uses it, and at what scale?
• Public link or screenshot if you can share one

The memory / state problem you hit

• What did you try first? (chat history stuffing, vector DB, graph, custom store, none of the above)
• Where did it break? (token limits, stale context, hallucinated history, lost preferences, no provenance, no portability, eval pain, governance / deletion)
• What was the moment you decided you needed something different?

Current workaround (or what Statewave is replacing)

• What's the system today, and what about it isn't working?

Where Statewave fits (or could fit)

• Which Statewave primitives map to your use case? Episodes, memories, ranked context, timeline, handoff packs, health/SLA, webhooks, something else?
• What's missing for it to fit cleanly?

Stack

• Agent framework:
• Model / provider:
• Embedding provider:
• Compiler mode:
• Storage:
• Deployment:

What we'll do with this

• Reply with concrete suggestions where we can
• Surface common patterns in roadmap updates
• Reach out (privately, if preferred) when something is a great fit for a deeper case study or design partnership

If you'd rather share privately — for example because the use case touches customer data or an unannounced product — reach out via the contact channels listed in SUPPORT.md (enterprise inquiries to enterprise@statewave.ai, licensing to licensing@statewave.ai).