A man with ALS has a brain implant that turns his thoughts into speech at about 50 words a minute, and he still couldn't start it by himself. He can't use his hands, so somebody else had to tap "record" for him. Neuralink engineers spent 72 hours in his home to fix that. By the time they left, he was taking his own phone calls. That button was really a person, by the way. A family member, a caregiver, whoever happened to be in the room every time he wanted to say something. The team shipped 30+ versions of the app in those three days, which Neuralink says is 2-3 weeks of progress. The first fix lets the system tell on its own when he's trying to speak and when he's just sitting there, so nobody has to tap anything. Then they piped his decoded voice straight into iPhone calls, injected…Read original on X
StoryFirst seen
Neuralink engineers spent 72 hours at a patient's home for setup
The patient cannot use his hands, so he could not start the brain implant alone and needed engineers on site.
Everything it touches
3 names 1 voices 1 source posts
The story’s neighborhood
Explore the graph, or choose a connection below.
Follow the evidence
The source posts
This brief comes from Tech Twitter’s edited headlines. The posts below are the sources grouped with the story; statements in them belong to their authors.
How the headline evolved
Neuralink engineers spent 72 hours at a patient's home for setup
Neuralink engineers spent 72 hours at patient's home on speech implant
Shared connections
Related stories
Grok Bot usage quotas reset as fixes roll out
Users reported hitting full usage limits before the reset, which came as fixes were being shipped.
Grok Bot changes underway to cut token use and improve behavior
Developers who built workflows on the bot are being asked to send feedback as the changes roll out.
Democrats plan investigations into SpaceXAI, Meta and Apple
The probes would examine President Trump's use of Grok, putting AI platform dealings under congressional scrutiny.
Supabase now works with Grok Bot through Cursor for backend changes
Team members can request database changes in chat, and Cursor builds and runs them through the Supabase MCP server.