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
Hi everyone! I'm Sihab, a Software Engineer interested in contributing to Gemini CLI for GSoC 2026 — specifically the Performance Monitoring and Optimization Dashboard idea.
I've already set up the dev environment, ran the full test suite, and done a deep read of the codebase — particularly the telemetry infrastructure in packages/core/src/telemetry/. I noticed that many metrics like recordStartupPerformance(), MemoryMonitor, and tool execution breakdown are already defined but have no in-terminal UI surface yet.
A few questions for the mentor (@sehoon38 or whoever is available):
Is the /perf or /stats command the preferred entry point for the dashboard?
Is there a preferred in-memory aggregation strategy, or should it hook directly into the existing OTEL pipeline?
Are there any constraints on adding new React/Ink components to packages/cli?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone! I'm Sihab, a Software Engineer interested in contributing to Gemini CLI for GSoC 2026 — specifically the Performance Monitoring and Optimization Dashboard idea.
I've already set up the dev environment, ran the full test suite, and done a deep read of the codebase — particularly the telemetry infrastructure in packages/core/src/telemetry/. I noticed that many metrics like recordStartupPerformance(), MemoryMonitor, and tool execution breakdown are already defined but have no in-terminal UI surface yet.
A few questions for the mentor (@sehoon38 or whoever is available):
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions