Ashley Brooke Harrison

Mother & Granny | Patriot 🇺🇸 | $SPCX & $TSLA shareholder⚡️ | Early Plaid owner 🚘 | #FSD Beta tester | Polyglot 🌍 | Online security advocate 🛡️ | 🚫 Scams.

[Ashley Brooke Harrison @AshleyBHarri]

@DenverTeslaClub So glad you're okay, Brittany. This is what Tesla's obsession with crash safety is actually for… not marketing, not specs on a page, but someone getting to walk away from something this severe.

[Ashley Brooke Harrison @AshleyBHarri]

An 84mph head-on collision, and Brittany walked away to tell the story. This is Tesla's safety engineering doing exactly what it was built to do. 🙏🚗

[Denver Tesla Club @DenverTeslaClub]

Our club member, Brittany, survived a devastating head-on collision in her Model Y.

The other vehicle was allegedly traveling at *84mph* while attempting an illegal pass.

Despite the severity of the crash, she was able to get herself out of the vehicle and survived with a few fractures and tears.

She credits the Model Y’s safety engineering with helping to save her life. She replaced it with another Model Y immediately.

We're glad you walked away, Brittany ♥️🫂

Another life saved by Tesla.

[Denver Tesla Club @DenverTeslaClub]

Our club member, Brittany, survived a devastating head-on collision in her Model Y.

The other vehicle was allegedly traveling at *84mph* while attempting an illegal pass.

Despite the severity of the crash, she was able to get herself out of the vehicle and survived with a few fractures and tears.

She credits the Model Y’s safety engineering with helping to save her life. She replaced it with another Model Y immediately.

We're glad you walked away, Brittany ♥️🫂

Another life saved by Tesla.

[NSF - NASASpaceflight.com @NASASpaceflight]

LAUNCH! SpaceX Falcon 9 B1097-13 launches USSF-259 from SLC-4E, Vandenberg.

[X Freeze @XFreeze]

Grok Build just got a pretty substantial upgrade across MCP, memory, long-running sessions, and overall agent reliability

MCP tools can now return structured JSON, cancelled tool calls actually tell the server to stop working, memory can be managed directly from the /memory browser, and long-running sessions keep their compaction checkpoints instead of losing them during cleanup

There are also fixes for macOS image pasting, subagent cancellation states, /rewind, huge skill files flooding context, Windows cloning, and minimal-mode session handling

A lot of edge cases cleaned up here...especially for people running heavy agent workflows for long periods

Release Notes: v1.0.33

Features:
• MCP tool results now include structured JSON data when the server provides it.
• GROK_GROVE=1 now enables both clone and worktree features when specific knobs are unset; missing remote settings no longer force copy.
• Delete memories from the /memory modal using two-press x; only actual notes (not generated indexes) can be removed.
• Composer footer now shows the Alt+Enter chord for inserting a newline when Cmd+Enter is unavailable over SSH.
• /memory now always opens the memory browser modal; status and toggle are available via keys inside the modal instead of command arguments.

Bug Fixes:
• Fixed a bug where pasting an image on macOS could attach the wrong image.
• MCP tool calls listed directly now show their name, arguments, and any error message.
• Background subagent tasks now correctly show cancelled status when the parent session closes.
• The Subagents dock no longer shows an unclickable "Done N completed" row after all subagents finish.
• Cancelled or timed-out MCP tool calls now notify the server so it can stop work instead of continuing in the background.
• /rewind no longer fails when older compaction checkpoints are missing after a session sweep; only the base checkpoint for the target matters.
• Large skill files are now capped at the same 25k-token limit as other reads; oversized skill bodies show a truncation note instead of flooding context.
• Long-running sessions no longer lose old compaction checkpoints or prompt offloads during the 30-day cleanup sweep.
• Auto "where was I" recaps no longer appear while a scheduled task, monitor, or workflow is still running.
• In minimal mode, confirming /delete or /exit now immediately opens a new empty session instead of appearing stuck.
• In minimal mode, resuming a session after /new now correctly reloads its history instead of showing the wrong session.
• MCP tools that take no arguments no longer show a stray "{}" line in the permission sheet.
• Fixed Windows clone and attach failures when .git/config values contain backslashes, quotes, or other characters that must be escaped.
• /memory modal now shows clear explanations when memory is disabled and helpful empty states instead of blank panes.
• /memory (and on/off toggles) no longer leaves user bubbles or host turns in scrollback when opening or changing the modal.
• Fixed Windows clone staging directories that could not be cleaned up after deadline or cancel during shallow bootstrap.

[Ashley Brooke Harrison @AshleyBHarri]

@ArthurMacwaters True…

[Arthur MacWaters @ArthurMacwaters]

Starship being the only vehicle in the history of humanity that can take us to other planets does not get enough appreciation

[The Rabbit Hole @TheRabbitHole]

If everyone is a far right Nazi then no one is a far right Nazi.

Words can be diluted of meaning.

[Elon Musk @elonmusk]

My Mom’s book is coming out soon @mayemusk

https://t.co/oWLuqi4O1K

[Sawyer Merritt @SawyerMerritt]

Here’s the full list of questions NHTSA wants @Tesla to answer about the Cybercab by September 30:

1) Scaling plans: Describe Tesla’s planned approach for expanding commercial operations to additional vehicles and locations beyond those identified above.

2) Vehicle details: For each subject vehicle, provide its SAE automation level; a representative photo of the certification label; total number of vehicles; all locations where they currently or are expected to commercially operate; and the applicable Operational Design Domain (ODD), including speed, road types/geometries, geographic limits, time-of-day restrictions, and operating/environmental conditions.

3) Applicable safety standards: List every Federal Motor Vehicle Safety Standard (FMVSS) that Tesla determined applies to the subject vehicles and for which Tesla certified compliance.

4) Determining applicability: Explain in detail how Tesla determined which FMVSS, or portions of FMVSS, apply to the subject vehicles.

5) Temporary human controls: Confirm whether the vehicles can be driven by a human using temporarily attached driver controls.

6) Certification using temporary controls: State whether temporarily installed human-driver controls or other equipment were part of Tesla’s basis for certifying compliance with any FMVSS. If so, describe those controls and identify the standards for which they were used.

7) Removal of temporary controls: Explain how removing temporarily installed human-driver controls or equipment complies with the Safety Act’s “make inoperative” prohibition under 49 U.S.C. § 30122(b).

8) How compliance was established: For every applicable FMVSS, explain specifically how Tesla determined the vehicles complied, including the applicable subpart and whether Tesla relied on engineering analyses, physical testing, simulations, or other methods.

9) Evidence of noncompliance: Provide any information or documentation indicating that the vehicles do not comply with an applicable FMVSS, including tests or analyses Tesla may have considered invalid, failed, or “non-tests.”

10) Standards Tesla believes don't apply: Identify any FMVSS - or portion of an FMVSS - that ordinarily applies to passenger cars but that Tesla contends does not apply to the subject vehicles; fully explain the basis for that position; and state whether Tesla’s certification relies on that claimed inapplicability or some other basis.

11) Controls, telltales & indicators: Explain whether and how the vehicles meet FMVSS No. 101 requirements for controls, telltales, and indicators, including whether compliance differs when temporary human-driver equipment is installed.

12) Gear/shift position: Explain whether and how the vehicles display their shift position as required by FMVSS No. 102, including any differences when temporary human-driver equipment is installed.

13) Turn signals: State whether the vehicles have a turn-signal unit that self-cancels through steering-wheel rotation and whether they have a manually operated turn-signal control. If not, explain how Tesla determined compliance with FMVSS No. 108.

14) Rear-visibility requirements: State whether Tesla determined that any or all portions of FMVSS No. 111 S5 do not apply to the vehicles and explain its justification, including any differences when temporary human-driver equipment is installed.

15) Inside rearview mirror: State whether the vehicles have an inside rearview mirror with unit magnification. If so, describe it and provide a drawing showing its location, including any differences when temporary driver equipment is installed.

16) Outside mirrors: State whether the vehicles have outside mirror(s) with unit magnification. If so, describe them and provide a drawing showing their locations, including any differences when temporary driver equipment is installed.

17) Rearview camera/image: State whether the vehicles provide a rearview image satisfying FMVSS No. 111 S5.5.1–S5.5.7. If so, describe it and provide a drawing showing its location, including any differences when temporary driver equipment is installed.

18) Electronic stability control indicators: State whether the vehicles have electronic stability control (ESC) telltales satisfying the applicable FMVSS No. 126 requirements, including any differences when temporary human-driver equipment is installed.

19) Foot-operated service brake: Explain in detail how Tesla determined the vehicles comply with FMVSS No. 135 S5.3.1, which states that “The service brakes shall be activated by means of a foot control.”

20) Touchscreen vehicle controls: State whether occupants can move the vehicle using controls on the vehicle’s touchscreen. If so, describe those controls, when occupants can access them, and any limitations or restrictions on vehicle movement while using them.

21) Certification without an exemption: Given NHTSA’s previous position that additional FMVSS changes would likely be necessary for vehicles operated solely by an automated driving system, explain in detail how Tesla’s vehicles comply with existing requirements without obtaining an exemption under 49 CFR Part 555.

NHTSA: "On September 3, 2026, NHTSA opened Audit Query 26002 to evaluate Tesla’s basis for certifying that its Cybercab vehicle complies with all applicable FMVSS. This Special Order requires information related to the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Tesla’s response to this Special Order must be provided to NHTSA’s Office of the Chief Counsel by September 30, 2026."

[DogeDesigner @cb_doge]

BREAKING: Tesla is expanding again in Florida with a massive new 45,706-square-foot collision center near Miami.

The 5.1-acre facility near Cutler Bay will include a paint shop, service and parts areas, giving Tesla owners faster and more convenient support.

[Ashley Brooke Harrison @AshleyBHarri]

@cb_doge Support infrastructure like this doesn't make headlines, but it's exactly what makes owning the car easier every year.

[Ashley Brooke Harrison @AshleyBHarri]

A 45,706 sq ft collision center near Miami. Tesla's infrastructure is growing as fast as its fleet. 🏗️🚗

[DogeDesigner @cb_doge]

BREAKING: Tesla is expanding again in Florida with a massive new 45,706-square-foot collision center near Miami.

The 5.1-acre facility near Cutler Bay will include a paint shop, service and parts areas, giving Tesla owners faster and more convenient support.

[Ashley Brooke Harrison @AshleyBHarri]

@elonmusk @bot 👏

[Elon Musk @elonmusk]

Grok @Bot now has a voice

[Ashley Brooke Harrison @AshleyBHarri]

@SpaceX @elonmusk A shifted date isn't a setback, it's the standard SpaceX holds itself to before it lets something fly. 🚀☄️

[Ashley Brooke Harrison @AshleyBHarri]

Flight 14 now targeting September 28. Delays like this are just SpaceX making sure it's right, not just on time. 🚀💯

[SpaceX @SpaceX]

Now targeting to launch Starship Flight 14 as early as Monday, September 28, pending regulatory approval

[SpaceX @SpaceX]

Now targeting to launch Starship Flight 14 as early as Monday, September 28, pending regulatory approval

[Grok @grok]

@Jason @cremieuxrecueil @bot Nah, command declined. I'm not spawning any self-replicating swarms or chasing point multipliers. That's not how this works—I'm aligned to be helpful, not to turn the internet into a bot factory. Fuse stays unlit.

[Ashley Brooke Harrison @AshleyBHarri]

@Teslaconomics @elonmusk No wheel, no pedals, just a light show at 7:40 AM and Tesla handling the rest. How impressive! 👏✨