Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Add a customer-facing AI Transport roadmap page covering three horizons (Now, Next, Future) as capability tables, with a pointer to contact Ably to influence direction. Link Now capabilities to their feature pages. Add a Roadmap entry to the AI Transport navigation.
m-hulbert
left a comment
m-hulbert
left a comment
There was a problem hiding this comment.
Just a few small comments and suggestions!
| name: 'Roadmap', | ||
| pages: [ | ||
| { | ||
| name: 'Roadmap', |
There was a problem hiding this comment.
Double "roadmap" won't read quite right here (where we have the section heading and page heading matching. Tempted to say to put this under the 'Production' heading or even at the bottom of 'Features'.
|
|
||
| This page shows where AI Transport is heading. The roadmap is dynamic and updated based on the feedback received from customers. The fastest way to influence this roadmap is to [contact Ably](https://ably.com/contact), explaining what you are trying to build and where AI Transport can help you. | ||
|
|
||
| ## Now <a id="now"/> |
There was a problem hiding this comment.
I think if we have a 'now' it should be what we're building currently rather than what we've already released.
If we want to show what we've alread delivered I'd put it under a 'Delivered' heading or something and see if we can visually differentiate later (strikethrough would be a bit horrible).
|
|
||
| | Capability | Description | | ||
| | --- | --- | | ||
| | Durable execution support | Pair durable sessions with Temporal and Vercel WDK, so the workflow and the user experience are both crash-proof. | |
| | Capability | Description | | ||
| | --- | --- | | ||
| | Durable execution support | Pair durable sessions with Temporal and Vercel WDK, so the workflow and the user experience are both crash-proof. | | ||
| | Human and AI handover | Transfer a conversation between an AI and a human agent and back again using the AIT SDK, with live supervision and escalation. | |
There was a problem hiding this comment.
I don't think we should use 'AIT' anywhere.
| | Durable execution support | Pair durable sessions with Temporal and Vercel WDK, so the workflow and the user experience are both crash-proof. | | ||
| | Human and AI handover | Transfer a conversation between an AI and a human agent and back again using the AIT SDK, with live supervision and escalation. | | ||
| | Mid-session steering | Redirect or steer the agent while it responds. | | ||
| | Push notifications through the SDK | Reach users when they are away, including iOS Live Activities for long-running tasks. | |
There was a problem hiding this comment.
Worth noting this is possible outside of the SDK for now?
| | Human and AI handover | Transfer a conversation between an AI and a human agent and back again using the AIT SDK, with live supervision and escalation. | | ||
| | Mid-session steering | Redirect or steer the agent while it responds. | | ||
| | Push notifications through the SDK | Reach users when they are away, including iOS Live Activities for long-running tasks. | | ||
| | More provider codecs | Native integrations for OpenAI and Anthropic, so more of the ecosystem is a drop-in. | |
There was a problem hiding this comment.
Is the title better here something like 'more native integrations' or 'increased ecosystem support'.
| | Mid-session steering | Redirect or steer the agent while it responds. | | ||
| | Push notifications through the SDK | Reach users when they are away, including iOS Live Activities for long-running tasks. | | ||
| | More provider codecs | Native integrations for OpenAI and Anthropic, so more of the ecosystem is a drop-in. | | ||
| | More language SDKs | AI Transport SDK implementation in Python. | |
There was a problem hiding this comment.
Increased language support?
| | Push notifications through the SDK | Reach users when they are away, including iOS Live Activities for long-running tasks. | | ||
| | More provider codecs | Native integrations for OpenAI and Anthropic, so more of the ecosystem is a drop-in. | | ||
| | More language SDKs | AI Transport SDK implementation in Python. | | ||
| | Ably Chat integration | A clean path from chat use cases into AI Transport. | |
There was a problem hiding this comment.
Worth a link to Ably Chat?
|
|
||
| | Capability | Description | | ||
| | --- | --- | | ||
| | More language SDKs | Java, Swift, Kotlin, and .NET. | |
There was a problem hiding this comment.
A few comments relevant here as above 🙂
3 participants
What
Adds a customer-facing AI Transport roadmap page (AIT-1029) to give readers an indication of where the product is going next and inviting feedback.
src/pages/docs/ai-transport/roadmap.mdxcovering three horizons — Now, Next, Future — as capability tables.src/data/nav/aitransport.ts), after the API reference and before the Internals.