[changelog] [Added] Rovo Agent Connector — EAP to Preview

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
cli, tooling

Research direction

Start with the forge-spec requirement rows and the modules/manifest validation area mentioned in the issue. Check how recognized modules and agent2Agent protocol versions are represented, then run the relevant validation tests. Done means rovo:agentConnector requires A2A version 1.0, rejects 0.3, and is no longer treated as EAP-fenced.

Written by the indexing model from the issue text.

Description

upstream-changelog

GUID: CHANGE-3405
Published: Tue, 25 Aug 2026 05:51:09 GMT
Category: Added

What's changing

The rovo:agentConnector module has moved from EAP to Preview. Apps using it can now deploy to production and staging environments, enabling Marketplace listing. Key changes:

  • A2A v1.0 is now required — v0.3 is no longer supported. Apps still on v0.3 are rejected at deployment. Manifest must declare version: "1.0" under protocols.agent2Agent.
  • System user mentionability change — adding rovo:agentConnector makes the app's system user non-mentionable; the agent connector user takes its place. Forge CLI v13.3+ warns and prompts for approval at deploy time.
  • Requires Forge CLI v13.3+.

Impact on forge-sim parity

  • Manifest/modules: if/when forge-sim recognizes rovo:agentConnector, manifest validation should require protocols.agent2Agent.version: "1.0" and reject v0.3 (matching real deploy rejection). Now that the module is Preview (deployable to prod), it's in scope for simulation, not EAP-fenced.
  • Deploy semantics: the CLI approval prompt for the system-user mentionability change is a deploy-time behavior; low priority for the simulator but relevant if forge-sim's deploy path validates rovo modules.
  • Simulator area: modules / manifest validation (and potentially the deploy pipeline).

Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3405

  • forge-spec: update affected requirement rows (behavior change)
Dominant language
TypeScript
Stars
5
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ryanackley/forge-sim

All issues in ryanackley/forge-sim

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.