> ## Documentation Index
> Fetch the complete documentation index at: https://dev-docs.persona.hasanraiyan.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Not Yet Implemented & Roadmap

> The honest gap list for @personaai/runtime v0.5.1 — what's a real unclosed gap, what's an intentional package boundary, and what's planned next.

This is v0.5.1. Every SDK resource now has a route (see [Routes](/guides/runtime/routes)); what's
left is either a genuine unclosed gap or an intentional package boundary, not an oversight.

## Not yet implemented

<AccordionGroup>
  <Accordion title="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](/guides/runtime/reconnect#honest-limitation-single-process-in-memory-only)
    for the full explanation and today's sticky-session mitigation.
  </Accordion>

  <Accordion title="Fine-grained (per-user, per-action) permissions within an enabled capability">
    **By design, not a gap.** See [Capabilities](/guides/runtime/capabilities#coarse-grained-by-design).
    A capability is on or off per mount; anything finer belongs in `resolveUser` or a
    [hook](/guides/runtime/hooks), not the runtime.
  </Accordion>

  <Accordion title="Adapters beyond Next.js, Express, and NestJS">
    [`@personaai/nextjs`](/guides/nextjs/quickstart),
    [`@personaai/express`](/guides/express/quickstart), and
    [`@personaai/nestjs`](/guides/nestjs/quickstart) 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](/guides/runtime/quickstart#quickstart-raw-node-http).
  </Accordion>
</AccordionGroup>

## Roadmap

* **A pluggable `RunBroker` interface** for multi-instance reconnect/resume (Redis or similar,
  opt-in). See [Reconnect and resume](/guides/runtime/reconnect#honest-limitation-single-process-in-memory-only).
  Track [issue #229](https://github.com/hasanraiyan/agent-marketplace/issues/229).
* **More framework adapters** (Wave 2–3 of the [SDK ecosystem plan](https://github.com/hasanraiyan/agent-marketplace/blob/feat/ai/product-research/11-sdk-new/package-ecosystem.md))
  — [`@personaai/nextjs`](/guides/nextjs/quickstart),
  [`@personaai/express`](/guides/express/quickstart), and
  [`@personaai/nestjs`](/guides/nestjs/quickstart) have 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`](/guides/sdk-quickstart) and is itself meant to be
wrapped by a framework adapter. If you're deciding which layer to build against:

| Layer | Use it when |
| - | - |
| [`@personaai/sdk`](/guides/sdk-quickstart) | You want direct, typed access to every REST endpoint with no opinions about HTTP routing, streaming, hooks, or auth — e.g. an admin script, a background job, or you're building your own runtime-equivalent from scratch. |
| `@personaai/runtime` | You want a ready-made set of HTTP routes (chat streaming, threads, files, memory, admin surface) but your framework has no dedicated adapter yet, or you're building one. |
| [`@personaai/nextjs`](/guides/nextjs/quickstart) | You're building a Next.js app — one catch-all route handler mounts the whole runtime, and the same package re-exports the React hooks. |
| [`@personaai/express`](/guides/express/quickstart) | You want the shortest path to "mount this and it just works" inside Express — the published adapter wraps the runtime as a Router. |