正在加载视频...

视频加载失败

SpaceXAI engineer (ex-Cursor): "I keep Grok 4.6 in Cursor for the work I'm watching and hand the rest to 20+ GrokBot agents. I stopped watching those months ago everyone optimizes the prompt. the bill isn't in the prompt" In a 30-min session she walks the whole stack: the roster,...

18,840 次观看 • 21 天前 •via X (Twitter)

13 条评论

Movez 的头像
Movez21 天前

brilliant watch amgio, defo an amazing GrokBot workshop

Odd&Entertaining 的头像
Odd&Entertaining20 天前

I think for a lot of us the likely unlimited credits for a Cursor or XAI coder gives some great ideas, however we can't just "stop watching" the bots "months ago." I'm on Heavy, as well! I can't do that. I appreciate all the tips I can get though, for sure! 👏

Raunak Yadush 的头像
Raunak Yadush20 天前

The interesting part is shifting focus from prompts to orchestration and workflow design. That’s where agentic engineering gets serious.

@FLFren 的头像
@FLFren20 天前

is bait, my Goodman

catman 的头像
catman21 天前

the “20+ agents” claim is less interesting than the handoff: what decides a task is safe to delegate, and how do failures get surfaced back into Cursor?

AI Mastery Guide 的头像
AI Mastery Guide20 天前

20 bots and one word input, wild

kocer 的头像
kocer21 天前

this is actually useful the handoff part is the one people skip

bitroot.india 的头像
bitroot.india21 天前

Same for API teams. The 20$ seat is noise, the invoice is the 10k system prompt on every call and opus on tickets Haiku could classify Cache the prefix. Route the easy work. Batch what can wait.

Money Bunny 的头像
Money Bunny20 天前

the real cost hides in orchestration not the words you type

TH33ORACL3 𝕏 的头像
TH33ORACL3 𝕏21 天前

the prompt is free. the billing tab is where my character arc begins.

0xSlyth 的头像
0xSlyth21 天前

the real cost is trusting it to run

安叫兽|Bird🕊️ 🔶 BNB 的头像
安叫兽|Bird🕊️ 🔶 BNB20 天前

提示词卷半天,不如先算算代理并发和人工监控的账

Kuzka_aaa 的头像
Kuzka_aaa20 天前

The bill isn't in the prompt' is a sharp line. If prompt optimization isn't where the real cost lives, where does she say the actual budget leak happens — orchestration overhead, retries, or something else?

相关视频