docs(roadmap): refocus the public roadmap on the agent platform - #5515
Closed
mmabrouk wants to merge 1 commit into
Closed
docs(roadmap): refocus the public roadmap on the agent platform#5515mmabrouk wants to merge 1 commit into
mmabrouk wants to merge 1 commit into
Conversation
Replace the pre-pivot Playground and Evaluation entries in inProgressFeatures and plannedFeatures with the current agent-platform roadmap. shippedFeatures is left unchanged. Adds agent-era theme labels. Each new planned item links to a tracking issue (#5510-#5514); in-progress items link to existing issues/PRs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe roadmap data adds shipped-feature categories and replaces the in-progress and planned feature lists with updated entries, descriptions, links, and label colors. ChangesRoadmap updates
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Member
Author
|
superseded |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
The public roadmap page (
docs/src/data/roadmap.ts) still described the pre-pivot, prompt-management product. Its "in progress" and "planned" sections were Playground, Evaluation, and Observability items. This updates those two sections to reflect the pivot to an agent platform.shippedFeaturesis unchanged. It is the product's history and stays accurate. The agent-era shipped items (skills, agent self-modification, CRON and triggers, MCP servers, ask-for-connection, agent tracing) still need real changelog pages before they can be added, so they are left as a follow-up rather than linked to pages that do not exist yet.In progress (now)
Four current initiatives, each linked to its tracking issue or PR:
Planned (next)
Five capabilities. New tracking issues were opened for the four that had none, plus custom triggers:
Removed from the old lists: the pre-pivot Playground and Evaluation items (navigation between test sets, prompt snippets, open spans in the playground, evaluator playground updates, annotation-queue-to-test-set, creating agents from the UI), plus trace usage limits, prompt caching in the SDK, and tagging.
Labels
The new entries use agent-era theme labels: Agent Builder, Reliability, Approvals, Multimodality, Channels, Mobile, and the reused Tools & Triggers (orange). Colors are placeholders and easy to change. The roadmap page renders any label name generically and falls back to a default icon for names it does not recognize, so no page code needed to change.
How to review
Open
docs/src/data/roadmap.tsand read only theinProgressFeaturesandplannedFeaturesarrays near the bottom of the file. Everything above them, includingshippedFeatures, is untouched. Each entry is a small object with a title, a description, agithubUrl, and one label. Confirm the titles and descriptions read the way you want them shown on the roadmap page, and that eachgithubUrlpoints where you expect.Checks
tsc --stricton the file passes. ThePlannedFeaturetype requires agithubUrlon every entry, so each item links to a real issue or PR.🤖 Generated with Claude Code