Had a terribly dark thought that AGI entering the core of human civilization is like the pivotal moment when free-living bacteria first got engulfed by a cell and became mitochondria, and we are the mitochondria in the cells of the machine.
Sometimes all you need is a tiny push to keep yourself moving in the right direction at the right velocity. An olive branch carried back to the ark by a dove was enough for Noah.
I asked Kimi K3 to design a robot for deep sea research
Here's what it came up with
A jellyfish inspired robot with tentacles built from a hexagonal nanostructured lattice, designed to withstand extreme pressure.
I’m pretty convinced now codex is failing to create cache properly on some accounts.
I’ve been testing the exact same workflow across 3 accounts. Main account on sol high, and two others on max + ultra. The other accounts appear to be caching normally, while my main account burning through its limits way faster and got completely drained.
Something is definitely wrong with how cache is being handled across accounts.
everyone is looking at grok bot like it is five new employees
the more interesting part is that they are not five isolated employees
they share one persistent cloud environment: the same browser sessions, terminal, filesystem and authenticated tools - while a chief of staff can route work between them without waiting for you to open the laptop
that turns one login into infrastructure
a research bot can collect leads, pass them to a writer, hand the result to a designer and let an ops bot update the workflow all inside the same running machine
the upside is obvious: less copying, fewer handoffs and work that continues while you sleep
the blast radius is just as obvious:
- authenticate only the services the whole agent fleet is allowed to reach
- give every bot a narrow role description, because that description becomes its place in the org chart
- keep irreversible actions behind human approval: sending, publishing, spending and production changes
- store skills, configuration and long-term state inside `/workspace`, because the rest of the VM may disappear during an update
- treat shared sessions as shared authority, not as separate bot identities
the same architecture that makes grok bot useful is what makes it dangerous to configure casually
my take: the breakthrough is not that you can hire five AI workers
it is that they can operate like one persistent company inside your real tools and your job changes from prompting every task to designing the permissions, boundaries and handoffs
the full chief-of-staff setup, session handoff model, approval matrix and `/workspace` survival strategy are mapped out in the article ↓
im able to run experiments that would have taken me days in literally six seconds of active time mumbling the high level idea to a microphone and its just wild
Mercury is different and beautiful in its own way.
It has a global magnetic field, but its very weak. It is offset from the planet's equator and barely holds the solar wind this close to the Sun.
It's hard to think of a more influential modern artist than Moebius. It is insane how much people have copied from him. The way modern manga looks (Miyazaki was obsessed with him), the cyberpunk aesthetic, certain ways of drawing scenes.....
The human preoccupation with eliminating LLM hallucinations reflects an unwillingness to confront the fundamental incompleteness of all knowledge systems.