Connect with us
tesla-fsd-beta-10-69-2-3-release tesla-fsd-beta-10-69-2-3-release

News

Tesla FSD Beta 10.69.2 “looking good” for weekend release + 10.69.1.1 Reviews

Credit: Whole Mars Catalog/Twitter

Published

on

Elon Musk shared that Tesla FSD Beta 10.69.2’s release is still set for this weekend. 

Tesla initially planned to release v10.69.2 last week but delayed the update to polish it up more. The company rolled out v.10.69.1.1 to more Beta testers instead. 

Tesla FSD Beta 10.69.1.1 Reviews

A few Tesla Beta testers who received v10.69.1.1 shared their observations and thoughts about the update with Teslarati. One of the common issues Beta Testers mentioned was phantom braking. 

One 2021 Model S owner, Howard, noted that his Tesla vehicle still experienced phantom braking too much. He shared that his Model S drove like a 16-year-old. “Not smooth with the wheel, throttle, or brakes,” he said.

Howard also observed that his Tesla ignored some speed signs, even if they popped up on the display. The Tesla Model S owner added that his car “still fades right into turn lanes when there is not [a] turn to be done. It then swerves to go to the last [turn] it just left.” 

Fellow FSD Beta tester, Michael, was “a bit disappointed” with the latest update. He noted experiencing some phantom braking along the Long Island Expressway. 

Advertisement
-

“Can’t seem to figure out the somewhat irregular lines in the HOV lane, which is surprising to me. Oh well….hope for better next time. Still not there, but much better than first experiences,” Michael added. 

Impressions from a longtime FSD Beta Tester

FSD Beta tester Les also shared his thoughts about v.10.69.1.1 with Teslarati. Les has been an Early Access software tester since 2018. He was kind enough to break down all his observations from testing FSD Beta 10.69.1.1.

Les mentioned seeing a few issues with FSD Beta that have been around since Fall 2021. Some of the issues are listed below.

  1. [The] car doesn’t always stay in [the] proper turn lane when using the outer lane of a left dual turn lane scenario; 8/10 times, mid-turn, it will cross over into the inner turn lane. It has done this for me with every FSD Beta build back to October 2021. 
  2. Inconsistent lane selection: my car will still sometimes move[s] into lanes opposite to the next upcoming turn, sometimes when close to that upcoming turn, sometimes missing the turn itself.
  3. Late turn signals: this is a long-standing issue many testers have reported. The turn signals [usually] activate too late when they need to activate ahead of a turn lane to alert drivers behind us.

Despite the continuing issues he observed, Les seemed to have an overall good experience with the latest update. He specifically highlighted Tesla’s work with Chuck Cook Style’s unprotected left terms which were specifically mentioned in v10.69’s release notes. Listed below are all his good observations about FSD Beta v. 10.69.1.1.

  1. The improvement to “Chuck Cook style” unprotected left turns with multiple lanes and medians is incredible. The car utilizes the median space very well. [It] feels like more than an improvement. It really almost feels like a feature upgrade. It’s that significant and amazing to experience.
  2. The car has almost no more phantom braking events for me. I never had many to begin with, certainly not as many severe events as other friends report, but I did notice the ones I had and the places they occurred no longer occurred.
  3. Traffic turning across my car’s path no longer triggers a cautious braking event when there’s enough room ahead. The car better recognizes the crossing vehicle’s direction and speed, and my car maintains its speed. Very human-like behavior.
  4. More assertive and smooth acceleration out of turns, especially when entering a higher speed road. Related: improved acceleration from stops. I like this very much, as prior builds often took too long (for my taste anyway) to get up to speed. It still could get up to speed more quickly, but there is [a] notable improvement. 
  5. The dashcam bug has been eliminated!! The prior build would routinely crash the dashcam after I parked and/or charged, requiring either a computer reboot or removal/reinsertion of [the] dashcam thumb drive to fix. No more problems!

In general, Tesla is steadily improving FSD Beta with each update. And Testers are actively experiencing those improvements. However, Tesla’s Full Self-Driving suite still needs more work before it rolls out to the public. 

Are you an FSD Beta tester? I’d like to hear your thoughts on v10.69.2! Contact me at maria@teslarati.com or via Twitter @Writer_01001101.

Maria--aka "M"-- is an experienced writer and book editor. She's written about several topics including health, tech, and politics. As a book editor, she's worked with authors who write Sci-Fi, Romance, and Dark Fantasy. M loves hearing from TESLARATI readers. If you have any tips or article ideas, contact her at maria@teslarati.com or via X, @Writer_01001101.

Advertisement
Comments

Elon Musk

Grok Bot users hit with weekly limits early, Elon Musk explains what happened

Published

on

Credit: Grok Bot

Elon Musk said weeks ago during SpaceX’s third-quarter earnings call that the company’s Grok Bot, its autonomous AI Agent platform, was showing “the fastest growth of a product” that he’d ever seen in his life.

Now, SpaceXSI is scaling back Grok Bot users’ weekly limits, much to the surprise of those who have relied on it to take away monotonous tasks in their lives.

Elon Musk’s terse November 1 reply on X captured a sharp tension in the early days of agentic AI. Responding to a user who asked for a Grok Bot usage reset after hitting 100 percent with four days still left on the weekly cycle, Musk wrote: “The cost of serving Grok Bot was unsustainably high relative to revenue.”

The post arrived amid a wave of similar complaints from paying subscribers whose meters had jumped unexpectedly toward or to the limit, sometimes overnight and with little corresponding activity. It also stood in clear contrast to statements Musk had made only days and weeks earlier.

On the SpaceX third-quarter earnings call in mid-to-late October, Musk had described Grok Bot in almost the opposite terms. He called it “the fastest growth of a product that I’ve ever seen in my life” and said he had “never seen anything grow this fast.”

Company figures put paid weekly users at roughly 800,000 earlier in the month, more than doubling over the prior period. Daily active users had climbed from under 100,000 in early September to over 600,000 by late October.

Musk emphasized that the product has no free tier and that users appear to be getting real value beyond what they pay. In other remarks, he noted that usage per user was rising rather than declining, the opposite of the usual decay pattern for new software.

Grok Bot, launched around August, functions as an always-available agent with its own persistent cloud computer; it can schedule, research, shop, browse, and execute multi-step workflows even after the user steps away. Access is bundled into X subscription tiers (roughly $30, $100, and $200 per month) and certain Cursor plans, drawing from shared weekly usage pools whose exact sizes have not been publicly detailed.

The economics of that model are what Musk’s November 1 post put in the spotlight. Agentic systems burn far more compute than ordinary chatbot exchanges. Each task can trigger repeated model calls, tool use, web actions, and sustained background work.

When growth is as rapid as Musk celebrated, the absolute compute bill scales quickly even if average revenue per user stays fixed under flat monthly subscriptions. Industry observers noted the opportunity cost as well: the same GPUs can be rented to other AI labs at higher rates.

A simple back-of-the-envelope comparison circulating after the post illustrated the gap: if every reported daily user paid the top tier, annualized subscription revenue would still be modest relative to the scale of compute infrastructure SpaceX is building and leasing to companies like Anthropic.

Some users also reported possible dashboard anomalies around the same period, though Musk’s framing treated the underlying cost-revenue imbalance as the core issue rather than a pure metering glitch.

The juxtaposition is the core of this exchange. Within roughly two weeks of publicly framing Grok Bot as an unprecedented success with strong unit economics and no free tier, Musk acknowledged that serving the same product had become unsustainable relative to the revenue it generates.

For the broader industry, the episode underscores a structural challenge of the agent era: demand is real and growing faster than many expected, yet the cost of fulfilling that demand through always-on, multi-step agents can outrun subscription pricing before companies can adjust limits, introduce metered billing, or raise prices.

Musk’s reply did not promise an immediate reset or higher allowances; it simply stated the constraint. In doing so, it supplied a rare, explicit public data point on the unit economics of a high-profile AI agent just as adoption numbers were still being celebrated as the fastest in Musk’s experience.

The tension between rapid, paid growth and the compute required to deliver it is now on the record.

Continue Reading

News

Tesla owners who tap Emergency Drive Away for fun are in for a surprise

Tapping Activate on Tesla’s Emergency Drive Away reportedly triggers a $539 service bill without moving.

Published

on

By

Tesla owners who press Activate on Emergency Drive Away may be on the hook for a service bill even if their car never leaves the Supercharger stall.

Yaro, who posts about Tesla service cases on X as @Tutrifour, said a customer called after tapping Activate while still plugged into a Supercharger. The owner was about to pull away, remembered the cable was still connected and stopped. The car never moved, but the touchscreen showed a red alert reading “Emergency Drive Away has been activated” with “Service is required” underneath. A Service Mode screenshot showed the active alert BMS_a228_EmergencyDriveAwayServiceRequired, which Yaro said only Tesla Service can clear.


The cost of clearing it was the bigger surprise. “Don’t press Activate on the new Emergency Drive Away feature on your Tesla because service charges $539 to inspect the charge port and to clear the alert. Yes, even if you didn’t move the car an inch,” Yaro wrote.  The $539 figure comes from that single case, and Tesla has not published a set price for the inspection or commented on the post. Yaro also noted that the car would still charge with the alert on screen.

Tesla launched Emergency Drive Away on October 1 with software update 2026.38.3, letting drivers pull away from a U.S. Supercharger with the cable still attached, as Teslarati reported. To use it, a driver shifts into Drive while connected, holds the brake and taps Activate. The prompt warns that driving with the cable connected will damage the vehicle and the Supercharger, and that short camera recordings will be shared with Tesla.

Tesla Charging has been clear about what follows a real activation. Repairs to a Supercharger stall can run up to $25,000 depending on the site, a service visit for the car’s charge port is mandatory, and deliberate misuse “will invoke additional penalties.” What the company had not spelled out is that the service requirement is triggered the moment Activate is pressed, not the moment the cable breaks away.

From an engineering standpoint, that is the cautious choice. Once Activate is pressed, the car cannot be sure the charge port latch was not stressed, so flagging it for inspection removes the guesswork. It also means the button carries a price on its own, which is a stronger deterrent against casual use than any warning screen.


The report follows the feature’s first known real world use, when a driver in Austin during F1 weekend appeared to trigger it by accident and dragged the Supercharger cable along with the car. The Reddit user who filmed it said the driver seemed to have only half read the prompts.

For owners, the takeaway is to treat the red prompt as a stop sign. If it appears after shifting out of Park by mistake, shift back and unplug the normal way from the touchscreen, the Tesla app or the button on the charge handle. Activate is meant for moments when staying at the stall is the bigger risk, and Tesla is now pricing it that way.

Continue Reading

Elon Musk

Elon Musk calls Earth’s data centers “peanuts” next to what SpaceX is planning in orbit

Elon Musk says SpaceX capex efficiency is underestimated as orbital data centers loom by 2028.

Published

on

By

Elon Musk is pushing back on one of the biggest worries hanging over SpaceX stock. In a reply on X on Sunday, Musk said the company’s capital expenditure efficiency is severely underestimated. He was responding to a Milk Road Stocks post citing analyst Kyle Reidhead, who estimates SpaceX will need to spend roughly $470 billion over the next five quarters.

Reidhead built that figure around the target SpaceX set on its third quarter earnings call: 13 gigawatts or more of compute by the end of 2027. In his breakdown, Nvidia captures 83 to 89 percent of the spending. SpaceX ended the quarter with 1.7 GW of nameplate compute and guided to $35 billion to $40 billion in fourth quarter capex, as Teslarati reported.

Musk did not attach a number to his claim, but the earnings call shows the argument. CFO Bret Johnsen said new compute currently pays for itself in under a year at today’s pricing, and Musk said that window could shrink to six months next year. Using that pace, Reidhead argues about $230 billion of the $470 billion could come from operating cash flow and about $60 billion from SpaceX’s roughly $90 billion cash pile, leaving around $180 billion to borrow. Musk confirmed last week that SpaceX had already closed a new $40 billion debt raise to buy GPUs.

The ground buildout is not the end goal. It is what is meant to pay for the move to orbit. Replying on Friday to charts built from Sequoia partner Shaun Maguire’s SpaceX model, Musk wrote that “Terrestrial compute will be peanuts compared to orbital compute,” adding that orbital compute deployed per month “probably exceeds terrestrial around the end of 2028 and then far exceeds it in 2029.”

Maguire’s model shows how steep that path is. It has capex climbing from $88 billion this year to $290 billion in 2027 and $369 billion in 2028, with SpaceX burning $77.8 billion in cash this year and $122.6 billion next year before turning $114.9 billion cash positive in 2028. Musk’s response to the model was, “I think we can do better.”

Advertisement
-

The orbital half runs through Starmind. SpaceX plans to operate up to 1 million AI satellites flying in clusters of about 10, linked by roughly 10 terabits of bandwidth, with deployment of thousands of units starting as soon as late 2027 out of its Gigasat factory in Bastrop, Texas, according to SpaceX’s space safety page. Musk has said each Starmind spacecraft will carry more than 250 kW of solar power.

Getting there depends on launch volume. Maguire’s model assumes 250 Starship flights in 2028, up from two this year and 38 next year. The nearer test is financial: SpaceX guided to $33 billion to $37 billion in first quarter 2027 revenue, more than double the $14.58 billion it booked in Q3, and Musk reposted that guidance again on Sunday morning.

Continue Reading