Not yet implemented
Multi-instance reconnect/resume
Multi-instance reconnect/resume
The one real gap. Single-process resume is implemented and tested; sharing a live run across
separate runtime instances would need a message-broker architecture this package doesn’t
provide yet. See Reconnect and resume
for the full explanation and today’s sticky-session mitigation.
Fine-grained (per-user, per-action) permissions within an enabled capability
Fine-grained (per-user, per-action) permissions within an enabled capability
By design, not a gap. See Capabilities.
A capability is on or off per mount; anything finer belongs in
resolveUser or a
hook, not the runtime.Adapters beyond Next.js, Express, and NestJS
Adapters beyond Next.js, Express, and NestJS
@personaai/nextjs,
@personaai/express, and
@personaai/nestjs have shipped. @personaai/node,
@personaai/fastify, and @personaai/hono don’t exist yet. By design, not a gap: this
package is the foundation they’re meant to wrap, not a replacement for them. Until your
framework’s adapter ships, use the
raw Node http quickstart.Roadmap
- A pluggable
RunBrokerinterface for multi-instance reconnect/resume (Redis or similar, opt-in). See Reconnect and resume. Track issue #229. - More framework adapters (Wave 2–3 of the SDK ecosystem plan)
—
@personaai/nextjs,@personaai/express, and@personaai/nestjshave shipped; each remaining adapter should be a thin translation layer, proving the framework-neutral contract here is actually sufficient.
Package boundary, for reference
@personaai/runtime wraps @personaai/sdk and is itself meant to be
wrapped by a framework adapter. If you’re deciding which layer to build against: