What's New: Team Workspaces, Split Intelligence, and MCP Feedback

We have been shipping toward the team-and-monetization phase of the product plan. Here is a concise rundown of what is live or landing now, with pointers to docs and the changelog for ongoing updates.

Team workspaces

Organizations can create teams in the dashboard, invite members, and assign GitHub repositories to a workspace. For scripted and CI flows, rvue enable --team <slug> avoids interactive prompts. See Dashboard and CLI reference for details.

Split intelligence on disk

On-repo intelligence now lives in .rvue/ as split JSON files (for example conventions.json, anti-patterns.json, knowledge.json, reviewers.json, meta.json), optional proposals.json for pending MCP-suggested changes, plus generated Agent Skills and AGENTS.md. The CLI, cloud analyze API, and MCP server share a single merge path so updates stay consistent. Core concepts describes the model.

MCP: record feedback and approve proposals

The MCP server exposes tools to record feedback and approve proposals, so agents can suggest updates to conventions and teams can merge them into .rvue/ in a reviewable way. Install and tool list: MCP install and tools in the CLI docs.

Docs and dashboard

Documentation pages (quickstart, CLI, dashboard, configuration, concepts) have been aligned with the split-file layout, team assignment, sync, and metrics. The in-app experience for repo intelligence and team management continues to tighten alongside billing for team workspaces (pricing).

For a running list of releases, keep an eye on rvue.dev/changelog. If you are new to the product, Introducing rvue is still the best overview.