Just plain bicycles, actually.

The general idea of an EEG system that posts data to a network?

Very, but there are already tons of them at lots of different price, quality, openness levels. A lot of manufacturers have their own protocols; there are also quasi/standards like Lab Streaming Layer for connecting to a hodgepodge of devices.

This particular data?

Probably not so useful. While it’s easy to get something out of an EEG set, it takes some work to get good quality data that’s not riddled with noise (mains hum, muscle artifacts, blinks, etc). Plus, brain waves on their own aren’t particularly interesting—-it’s seeing how they change in response to some external or internal event that tells us about the brain.

Simplification can be good---but they've removed the wrong half here!

The notifications act as an overall progress bar and give you a general sense of what Claude Code is doing: is it looking in the relevant part of your codebase, or has it gotten distracted by some unused, vendored-in code?

"Read 2 files" is fine as a progress indicator but is too vague for anything else. "Read foo.cpp and bar.h" takes almost the same amount of visual space, but fulfills both purposes. You might want to fold long lists of files (5? 15?) but that seems like the perfect place for a user-settable option.

Research is going up; clinical is going down.

The idea behind the recent boom in low-field stuff is that you'd like to have small/cheap machines that can be everywhere and produce good-enough images through smarts (algorithms, design) rather than brute force.

The attitude on the research side is essentially "por qué no los dos?" Crank up the field strength AND use better algorithms, in the hopes of expanding what you can study.

What's the minimum residency you'd accept, because 3-4 years seems quite long to me.