Robert Kelly retweeted
Grok @bot usage burns too fast!
We know, and we're on it.
Until then, here's what 572 of you said ate yours, plus a line you can paste to your bot for each:
> bots chatting with each other: "Only message other bots when you need something from them. Batch updates into one message. No thanks or ack replies."
> routines running too often: "Change this routine to once a day."
> stuck loops (the #1 complaint): "If you hit the same error twice, stop and tell me what's blocking you. Don't say done until you've checked."
> browser logins: "Use the connector if available, don't open a browser for this."
> image, video and voice: "Before you generate anything, tell me what you'll make and wait for my OK. Do one sample first."
> big coding or research jobs: "Give me a short plan first and wait for my OK. Do small tasks yourself, don't spin up helpers."
To see where yours went: "Check my usage and tell me which routines and bots used the most this week."
Like I said, we're still working hard on making usage easier to see, and cheaper where it should be.
Reply with what's burning yours and I'll look.
“The proper interface between government and private citizens and their corporations is rule of law.” - 💯
Stop trying to get people fired because they’re competition or you disagree with them politically.
Replying to @TimSweeneyEpic
The articles backtracked from their original incendiary, and now clearly false, claims to something more like "Jensen did lawful things that powerful people didn't like". It still appears the original claims came from a single competing Big Tech lobbyist.
The reporting successfully disrupted corporate governance processes, with a running cost of $1.8 trillion in losses to American pension funds and shareholders.
Here's what I fear is being lost in these articles: The proper interface between government and private citizens and their corporations is rule of law. Laws are passed, and if wrongdoing as alleged, then there's due process: an investigation followed by facts and evidence presented in open court. Due process should happen here: let the facts come out whole, and not as a trickle of dubious claims.
Press takedowns full of sketchily sourced claims and backtracking narratives are not the way. It's what we see outside of the free world, and is no model for The United States of America.
In particular, if the Jensen takedown succeeds on the basis of these journalistic failings, which is not by any means certain as Sam Altman's case shows, then it foreshadows an economically and institutionally ruinous new playbook to be adopted with no end in sight.
Imagine a weekly stream of takedowns emerging from opportunistic alignments between corporate lobbyists and political interests which, given the new partisan split between the executive and legislative branches, will attack in all directions, undermining not only the US economy but American leadership in the world.
I hope cooler heads prevail this coming week as they did not on Thursday November 12. And I urge anyone who happened to oppose Jensen, open models, and the underlying trade policies in question, to recognize that this isn't a win for "team regulation". It's a change in the game from a transparent rules-based one to a sinister new form centered around politicans and lobbyists.
24
I do expect some quid pro quo here. If we paid $8k 2.5 years ago, that equaled about ~47 shares of Tesla stock at the time. That would be worth ~$18k today. That should buy us FSD - “Unsupervised” FSD was what we were investing in because
1. That’s what was marketed and
2. We believed it would arrive within the useful lifetime of the car.
People who paid for FSD outright will probably get to use unsupervised at a discounted rate or even free.
People thought FSD was expensive at $8,000… but 1 year of unsupervised costs $3,600! It’ll pay for itself in a couple of years.
1
47
Not sure if I’m supposed to call and check!?
User reports indicate problems with 911 since 4:13 PM EST.
How is it affecting you? #911Down
downdetector.com/status/911/
24
Many people share honest reasons why we shouldn’t build data centers. Unfortunately, they are not truthful, logical, or intelligent reasons.
18
You may have joined the cool kids club building a software factory. So, are you "the foreman", or should you be working at a higher level now with the expectation the factory will change and adapt for the results you want?
Most enterprise software factories I see are still being built on assumptions made six months ago. Right now, six months is a long time.
Most try to give every team the same paved road. Engineering and architecture groups build it and expect everyone to use it. They standardize the a pipeline, enforce guardrails, and hope teams ship. It's the right goal, but the people and the work aren't all the same. Some products deploy daily. Others never need a build, just fast feedback. Teams work on different architectures that absolutely should be changing.
And much more building now happens outside the engineering org, with business users prototyping ideas to show what should get built or creating personal products that previously wouldn't exist. There's been a 100x+ increase in internal, temporary products with no support model that only need to live a few weeks. That pattern isn't going away and may be the biggest need for the organization.
A factory built around just one of those paths ignores the others. They may need to blend as business needs evolve, but a factory that can't change only serves people it was built for and won’t help the others.
So the answer likely isn't one factory. It's a factory of factories, with an orchestration layer that knows which fits each idea and keeps adapting as the work and people change. It's more than CI/CD with a security scan and automatic bug fixes. It's how any idea becomes working software, whoever it comes from.
You won't only be working with a ticket queue or through code changes. You'll reach it through a personal agent. Your agent will work with the foreman who can adjust the factory to your needs. Either way, you're dealing with something above the whole system, a higher abstraction than most factories built so far.
We've talked about the human in the loop, then above the loop. I think it goes further. The human guides the system that runs the factory and its many value streams. You set direction, give the system context and access, and let it correct itself. As building gets faster, that context and access become the real constraint.
This is how I'm working today on my team and it has been an amazing unlock. My factory is different than theirs and I work at a higher level of abstraction for the products I'm building.
I believe what will last will be the factories where you can actually "talk" to a foreman and expect the work to get done. They need to work for you, adapt, keep listening, and change without retooling everything.
The value of a factory will be its ability to mold to our needs. It's the intent and outcomes that matter, not the factory itself.
What do you think? How are you building your factory today? Will it adjust and grow as everyone's needs change?
3
60
I'm fine with it and more than willing to pay for what we use, but as far as I can tell I can't buy more Grok Bot usage on our team plan since it's a different usage model. Thoughts?
1
1
34
I hear if you use Copilot, you can also now use Copilot in Copilot with Copilot. Just ask Copilot.
1
18
Anyone who says, “this is our process”, “these are our tools”, “these are our models”, or “this is our policy” needs to understand you are proven wrong within 2-3 months.
It’s almost incomprehensible how wide the distance is between someone who’s working at the frontier with AI and basically everyone else right now.
The crazy thing is these lines are not converging, but only growing farther apart. If the curve of AI progress had leveled off, it would certainly have given most people and companies time to catch up or implement their workflows in a standardized way. The technology would have neutralized competitive advantage because everyone would be using it the same way.
But what’s happened is the opposite. The curve of AI progress is basically going vertical right now, which means if you had codified your processes 3-6 months ago you’re likely already behind again. Now imagine most companies that kicked into gear a year ago and thought that they were done. Even further behind now.
I’ve never seen a technology in my life and career that improves at this rate, which consequently means you need to upgrade your expectations at a similar rate. Our brains weren’t wired for this, and our organizational change management processes certainly weren’t either.
With any form of recursive self improvement, things just get wilder. It’s a time when you will need to be constantly reevaluating the things that didn’t work just a couple months ago to see if they now can be solved. AI native companies certainly have a strong advantage due to this right now, so now it comes down to can the bigger companies keep up. Wild times.
3
294
Robert Kelly retweeted
It’s almost incomprehensible how wide the distance is between someone who’s working at the frontier with AI and basically everyone else right now.
The crazy thing is these lines are not converging, but only growing farther apart. If the curve of AI progress had leveled off, it would certainly have given most people and companies time to catch up or implement their workflows in a standardized way. The technology would have neutralized competitive advantage because everyone would be using it the same way.
But what’s happened is the opposite. The curve of AI progress is basically going vertical right now, which means if you had codified your processes 3-6 months ago you’re likely already behind again. Now imagine most companies that kicked into gear a year ago and thought that they were done. Even further behind now.
I’ve never seen a technology in my life and career that improves at this rate, which consequently means you need to upgrade your expectations at a similar rate. Our brains weren’t wired for this, and our organizational change management processes certainly weren’t either.
With any form of recursive self improvement, things just get wilder. It’s a time when you will need to be constantly reevaluating the things that didn’t work just a couple months ago to see if they now can be solved. AI native companies certainly have a strong advantage due to this right now, so now it comes down to can the bigger companies keep up. Wild times.
We’re about to find out a “lab” was responsible and more regulation is required.
Replying to @cryptoblaney
Super intelligence agents will at some point do this to gain currency for themselves, not a human
14
I built a @bot to get all the AI/SI news every day. 200+ X profiles/accounts. Use it or make it your own.
Check it out. x.ai/bot/HsQr5Tf3yZ8Nr54O-hs…
2
50
Robert Kelly retweeted
Cursor can now control your computer.
Agents can drive desktop apps like the iOS Simulator to test the features they build.
Liatrio is a @SpaceXSI Launch Partner. 🚀 Let’s go build 🚀
We’re bringing together Grok and our Forward Deployed Engineers to support enterprise teams as they turn AI capability into software that ships.
We embed alongside your engineers, work on your backlog, and build the workflows and skills your team needs to keep moving after we leave.
This partnership's measure of success: client outcomes.
Robert Kelly retweeted
keeping up with AI is a full-time job. that's why every company needs a frontier team:
the frontier team's job is to keep up as models change. everyone else's job is to use what they learn
we made one @Every and it's completely changed how we work:
0:00 Introduction: Why every company needs a frontier team
2:42 Why the best frontier teams have pirates and architects
4:57 How Head of Evals @hammer_mt builds personal benchmarks
6:46 How Opus edited an explainer video using Slack messages and meeting notes
10:20 Working with AI means protecting other people’s attention
12:26 Why a frontier team needs a “wrangler” like Arielle Shipper
18:58 Why senior editor @jackcheng built a tabless browser
24:37 How resident writer @kplikethebird teaches her AI writing plugin who the reader is
30:51 Inside engineer @JannikJung’s personal AI orchestrator
35:41 Compound engineer @kieranklaassen uses AI to build power tools
21 people, a single meeting a week, no quarterly goals, no pull requests, no mandatory code review, no titles (except one dictator), a hundred releases a day, bugs fixed in minutes, famous for killing features.
@sqs and @thorstenball on how the Amp team works:















