You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a tracking issue for navigating the living public roadmap for Gemini CLI. If you are interested in following along with what we are doing, or even more exciting, looking to contribute. Please browse through here. Any items within are fair game and would be great contributions.
Effort Analysis:
The issue #4191 serves as the central 'Roadmap Issue' as documented in ROADMAP.md (lines 47 and 98). My investigation of the codebase via grep_search and glob confirms that there are no CLI commands or internal logic (e.g., in packages/core or packages/cli) that programmatically parse or display this roadmap. The issue's maintenance is restricted to updating text descriptions and linking to GitHub Project 11. This falls squarely under the effort/small guideline for 'Documentation & Strings' as it involves no architectural complexity, state management, or cross-component refactoring. The presence of kind/bug appears to be a mislabeling of a process-oriented tracking issue, as the body describes it as a navigational tool for contributors rather than a technical failure.
I have submitted PR #28960 to fix the trailing period bug on the Antigravity URL (#28052), which is part of the Core/Auth roadmap workstream. The CLA is signed, tests are green, and it is ready for review!
This PR is just the first part of the larger Core/Auth + Capacity + Scalability workstream. We have solved this initial issue and are actively working on the rest of the related problems in this workstream now.
@iamkartik0704 Thanks for taking interest but this issue is already assigned. We'd still love to have you contribute. Check out our Help Wanted list for issues where we need some extra attention.
The initial workstreams tracked here are outdated and refer to 2025 and Q1 workstreams. Closing as resolved as the majority work here has been concluded. Thank you for your contributions!
Activity
48 remaining items
gemini-cli commentedon Jun 27, 2026
Effort Analysis:
The issue #4191 serves as the central 'Roadmap Issue' as documented in
ROADMAP.md(lines 47 and 98). My investigation of the codebase viagrep_searchandglobconfirms that there are no CLI commands or internal logic (e.g., inpackages/coreorpackages/cli) that programmatically parse or display this roadmap. The issue's maintenance is restricted to updating text descriptions and linking to GitHub Project 11. This falls squarely under theeffort/smallguideline for 'Documentation & Strings' as it involves no architectural complexity, state management, or cross-component refactoring. The presence ofkind/bugappears to be a mislabeling of a process-oriented tracking issue, as the body describes it as a navigational tool for contributors rather than a technical failure.jeelsoni01 commentedon Aug 20, 2026
/assign
gemini-cli commentedon Aug 20, 2026
👋 @jeelsoni01, you've been assigned to this issue! Thank you for taking the time to contribute. Make sure to check out our contributing guidelines.
jeelsoni01 commentedon Aug 20, 2026
We have started working on this issue #4191
jeelsoni01 commentedon Aug 30, 2026
I have submitted PR #28960 to fix the trailing period bug on the Antigravity URL (#28052), which is part of the Core/Auth roadmap workstream. The CLA is signed, tests are green, and it is ready for review!
jeelsoni01 commentedon Aug 30, 2026
This PR is just the first part of the larger Core/Auth + Capacity + Scalability workstream. We have solved this initial issue and are actively working on the rest of the related problems in this workstream now.
iamkartik0704 commentedon Oct 10, 2026
/assign
gemini-cli commentedon Oct 10, 2026
@iamkartik0704 Thanks for taking interest but this issue is already assigned. We'd still love to have you contribute. Check out our Help Wanted list for issues where we need some extra attention.
[-]Public Roadmap[/-][+]2025 Public Roadmap Tracking[/+]DavidAPierce commentedon Oct 12, 2026
The initial workstreams tracked here are outdated and refer to 2025 and Q1 workstreams. Closing as resolved as the majority work here has been concluded. Thank you for your contributions!