Music Blocks/2026-01-18-meeting

Ashutosh: Asked for thoughts on how to continue a PR; mentioned taking on his PR today, implementing the shortcut, and integrating the CodeRabbit AI for Music Blocks.

Devin: Highlighted that MB performance (load times, etc.) is the top priority bug, and caching for users’ projects is also a problem.

Suryaansh: Asked about the MB4 meeting (told to tag Anindiya and remind them), mentioned tagging issues that could be closed and are solved, asked if the current PR was resolved and how to handle the block, and explained Lighthouse.

Vyagh: Discussed implementing lazy loading and the PR for the “Stop” button functionality; gave updates about package dependency PR work; discussed Control K widget additions in Music Blocks; talked about CodeRabbit implementation and documentation.

Divyam: Explained that MB can be hard to use since it doesn’t show what each block is used for and kids don’t understand bool, etc.; noted that the Music Blocks guide link shows 404.

Walter: Likes the idea of a tutorial but emphasized performance is a higher priority; suggested Shreya and Om S. schedule a separate call to discuss AI ideas.

Krishna: Asked about animation-related PRs.

Jetshree: Suggested that some PRs may affect performance and recommended adding Lighthouse performance checks.

Haroon: Asked for updates on MostlyK projects and suggested contributors include small demos for their fixes/features to make reviews easier.

Shreya: Discussed CodeRabbit and BuildPulse as AI integration ideas and asked about other areas in Music Blocks where AI could add meaningful value aligned with GSoC expectations.

Stuti: Talked about the undo inner-block bug, was advised by Walter to keep track of block states, and is reviewing AI API key availability to include an AI-powered mode in a feature.

Syed: Discussed about collisions in MBv4 and asked other query regarding V4.

Hari: Asked updates on MB4, discussed about scrolling for text heavy pie menus.