小栗说车日常记

后备箱的隔板设计，影响装载的灵活性｜购车分享 @mothio1201

[plusxbt @plusxbt]

It is becoming f*cking dangerous:

Oracle wanted $8.8B from Google.
for ~11,500 lines of Java API.
Supreme Court: fair use. 6 to 2.

now your agent can read an app you own.
no source code. with proof.

The idea: REA reads the panel on disk.
Opus 5.5 writes the spec.

the whole engine: 5 settings.

→ cut the frame 30 to 70%
→ cut each half again
→ stop after 5 cuts
→ re-cut on every beat

every cell is u v w h.

REA reads. Opus writes. you build.

behavior crosses over. code doesn't.

save this before you renew your next plugin ↓

[CELSIUS Energy Drink @CelsiusOfficial]

the shirley temple to energy drink pipeline is real

[小栗说车日常记 @fallenangel130]

@raqueloser 临汾那边等实测的我记下了，长途报告我攒够一趟就跑，你们平时跑哪条线多？

[小栗说车日常记 @fallenangel130]

太原这台Piaggio大踏板像精致职场姐姐，车身有体量，坐姿却舒服，城市和快速路都能切换得很自然。大同、晋中、临汾想看通勤与长途表现，主页继续。

[小栗说车日常记 @fallenangel130]

@AlexaCouturex3 哈哈哈能推翻一点刻板印象就值了，不过也别全信我，自己试一圈最准。

[小栗说车日常记 @fallenangel130]

@kiras89 大同冬天确实得想想，我这边还没跑过零下的实测，你是在大同冬天骑吗？

[小栗说车日常记 @fallenangel130]

@fUCKOFDEATH 你说得对，我标题说得顺了点，市区掉头确实得留提前量，车身体量在那摆着，小路口我也得慢一手。

[小栗说车日常记 @fallenangel130]

@sweetbubblegum8 是吧，这个点确实卡人，关键是它切起来不是硬切换那种，你平时主要跑哪段路多？

[小栗说车日常记 @fallenangel130]

@okhris 一百巡航车身挺稳，不飘；风挡挡胸口基本到位，但脖子和头盔附近还是有风感。你常跑哪段快速路？

[小栗说车日常记 @fallenangel130]

@jaimebear127 哈哈套装哪能少，我平时就头盔加个轻薄雨衣塞座桶，通勤够用了。你是想往精致路线搭还是偏实用？

[小栗说车日常记 @fallenangel130]

@smoney329 太原冬天确实考验人，我骑下来手套箱那边风不算冲，但原厂导流偏短，真要天天早晚通勤还是加个手把挡风更实在。你平时骑车通勤有多远？

[小栗说车日常记 @fallenangel130]

@RaNdArAyY 对，坐上去就不想下来这点我最有感，堵车时反而成了休息时间哈哈。你说的钻车缝灵活，是不是因为轴距和重心分布的关系？

[小栗说车日常记 @fallenangel130]

@Tec_with_Luis the wet asphalt in this reflecting that neon sign differently at each glance

[Sprytix @Sprytixl]

THIS IS A PURE F*CKING GOLDMINE

Anthropic just shared one of the best tricks for Claude Code.

The idea: you stop writing agent configs by hand. One prompt, and Opus 5.5 writes the entire swarm for you.

By hand that is 16 prompts, 16 tool configs, 16 test harnesses and 2,312 lines you type yourself. Here you type one line.

You just launch Claude Code like this:

claude --model opus "build REA swarm ×16 for legacy/"

here's the split:
→ Opus 5.5 reads 578 files and splits them into 16 services
→ it writes 16 specs in parallel, 1,037 lines, no templates
→ every spec becomes one REA agent, one reverse-engineer per service
→ each agent gets tested as it lands, 3/48 checks already green at 3 minutes

the part everyone gets wrong: they hand-write every agent and then wonder why 16 of them drift apart.

here one architect writes all 16 specs from the same read of the codebase, so every agent is wired the same way and nothing gets forgotten.

REA is the piece doing the real work underneath: each agent reverse-engineers its own service, dry-runs on three files first, then writes its spec from what it actually found, not from what you guessed.

you wrote 1 line. Opus wrote 1,037.

Opus architects. REA reverse-engineers. The swarm builds itself.

JEV engineering is the same move one layer down: the forks that need no thinker (which service, which tool, retry or stop) go to JEV in milliseconds, and the architect only sees the ones that actually split

the full tree
> Opus 5.5 runs as architect, reads the repo and splits it into services
> it writes one spec per service, all 16 in parallel, from a single read
> every spec spawns one REA agent that reverse-engineers that service
> each agent dry-runs on a few files before writing anything
> specs get tested as they land, the architect monitors all 16 in flight
> Opus 5.5 deploys once every spec is ready
JEV routes micro-forks in milliseconds

paste the tree and this prompt into Claude Code ↓

"Rebuild my Claude Code setup around this tree:

1. Run the main session on Opus 5.5 as an architect that writes agent specs, never agent code by hand.
2. Point it at a repo, let it split the repo into services and write one spec per service, all in parallel from a single read.
3. Every spec spawns one REA agent that reverse-engineers its own service and dry-runs on a few files before writing anything.
4. Test each spec as it lands, never wait for all of them to finish first.
5. Add one rule to CLAUDE.md: no agent ships until its spec passes its own checks.
6. Route deterministic forks (service choice, tool choice, retries) through JEV.

Show me every change as a diff first. No edits until I say go."

↳
https://t.co/GoHZ0potb7

save it, it'll come in handy.

[Argona @Argona0x]

holy sh*t. Karpathy's second brain pattern runs on Grok Bot now: stop explaining your life to AI from zero every chat, keep a wiki that writes itself

three bots in one group chat, each with its own memory:

the reader takes every link, PDF and voice note you drop and never edits it
the librarian rewrites every wiki page that source touches, usually 10 to 15 of them
the checker wakes up on a nightly routine and hunts contradictions, stale claims and pages nothing links to

→ you ask a question: the answer gets filed back as a page, so the brain grows from use, not only from reading
→ a new source contradicts an old page: the checker tags you instead of quietly overwriting it
→ a page goes 30 days without a fresh source: it gets marked unconfirmed

a second brain can sound sure while remembering the wrong thing

Reader collects. Librarian writes. Checker doubts.

every page has to show:
> the claim
> the source it came from
> the date it was last confirmed

paste this into Grok Bot:

"Build me a second brain with three bots in one group chat. Keep my sources untouched in raw/, maintain wiki/ yourself, file good answers back as pages and run a nightly check for contradictions. Show me the structure first. Do not create anything until I confirm"

start with one topic you actually work on, not your whole life

full setup below

[deezzex @deezzex]

I made GROK BOT my finance assistant.

your bank shows you where the money went. It never tells you where you're losing it

€19.99 subscription. €37 bad FX route. €23 in fees you never saw

now imagine an AI whose job is to find those every single day https://t.co/iFn5Yyc5Ip

[小栗说车日常记 @fallenangel130]

@deezzex Very well put

[opcodee @opc0de3]

THIS GUY IS A BUSINESS NOW

Pink shirt, green shorts, a balcony at night and "a lot of feelings"

28,015 likes and 503 comments on Instagram

There's already a memecoin built around this character. The views came first, the money followed

Would you ever buy a coin of a character?

[小栗说车日常记 @fallenangel130]

@francescoinweb3 This is really helpful

[cit1z3n @cit1z3n_]

One developer spent $1,305,088 on AI in thirty days.

Three people.
A hundred coding agents.
603 billion tokens.
7.6 million requests.

Peter Steinberger wasn't hacked.
He wired up the agents and let them run.

That was Fast Mode.
Turn it off and the same month is closer to $300,000.
Still $3.6 million a year.

OpenAI covered his bill.
He works there now.

Everyone else just gets the invoice.