Roadmap

This roadmap assumes Ageniti is already positioned as an SDK for building apps that agents can use.

The goal is not to add agent orchestration. The goal is to make adoption, release, and upgrade confidence much stronger.

P0 Must Ship

These are the highest-leverage gaps to close next.

1. End-to-end adoption path

A new team should be able to go from install to a working host integration without reading SDK internals.

Target outcome:

install the package
scaffold a host starter
run one action locally
connect the starter to a real host
export docs and manifests
build a distributable bundle

Acceptance bar:

one documented path works in under 10 minutes
one path covers an existing app
one path covers a host-oriented starter

2. Full project creation flow

init is good for adding Ageniti to an existing project. It is not yet the smoothest path for greenfield users.

Target outcome:

add ageniti create <template> <name>
generate package.json
generate install instructions or bootstrap commands
generate a runnable starter with one obvious next step

Acceptance bar:

a new folder can run without hand-written setup notes
the generated README explains how to verify success

3. Host-specific integration guides

The SDK now has examples and starters, but teams still need stronger production-facing guidance.

Priorities:

OpenAI Responses host
AI SDK route handler
MCP desktop host
HTTP gateway wrapper

Acceptance bar:

each guide explains auth boundaries
each guide explains risk filtering
each guide explains what belongs in the host versus the Ageniti app

P1 Should Ship

These additions improve trust and long-term maintainability.

1. Compatibility story

Teams adopting an SDK care deeply about what breaks when they upgrade.

Target outcome:

explicit action versioning guidance
deprecation policy
manifest diff examples in CI
release notes guidance for contract changes

Acceptance bar:

developers can tell whether a change is additive, risky, or breaking
reviewers can see contract drift before publish

2. Stronger release review tooling

The SDK should help maintainers review what is about to become public.

Target outcome:

surface exposure report
risk-focused linting
clearer publish checklist
generated summary of which actions reach which surfaces

Acceptance bar:

maintainers can review public exposure without reading source manually

3. Better operator debugging

When real hosts fail, teams need quicker diagnosis.

Target outcome:

clearer error taxonomy
invocation replay pattern
artifact inspection examples
doctor checks for common host integration mistakes

Acceptance bar:

common setup failures have direct recommendations
logs and envelopes are enough for first-pass debugging

P2 Nice To Have

These are useful once the adoption path and trust story feel solid.

1. More polished starters

richer READMEs
more realistic sample services
optional TypeScript variants
host-specific environment examples

dedicated docs hub for host integrations
dedicated docs hub for shipping and upgrade safety
recommended paths by user type

3. Demo-grade packaging

reference repos
recorded walkthroughs
hosted docs examples with final output screenshots

Suggested Execution Order

Finish one complete adoption path.
Add create for greenfield users.
Turn host-specific guides into production-focused docs.
Strengthen compatibility and release review.
Improve debugging and diagnostics.

Bottom Line

The next stage for Ageniti is not "more framework."

It is:

easier adoption
safer release
clearer upgrade path
stronger host guidance

That is what turns a capable SDK into a trusted one.

PreviousSDK Readiness Next Scope