curious about ai, robotics and art. design engineer at @heyglif. fun: https://nitter.cf/t.co/mEqjOEj5IJ
Berlin, Germany
Joined November 2013
- Tweets6.4K
- Following1.7K
- Followers3.3K
- Likes39.5K
Pinned Tweet
last night’s watercolor session with Claude! getting much better at trees now.
it also has a much bigger repertoire of brush strokes now, which enables it to compose drawings like this. and in addition, some cool new titration tricks.
Opus then used those brush movements to compose and paint “leeward”, an autumn tree leaning into the wind.
chrome extension version if you want to try it on any site: github.com/DhvanilPatel/swar… (original Swarm by Joel Califa)
also... taking prompt requests for the robot’s next painting :)
send me an image, a phrase, a mood, a colour -- or something stranger. curious to see what comes out of it!
last night’s watercolor session with Claude! getting much better at trees now.
it also has a much bigger repertoire of brush strokes now, which enables it to compose drawings like this. and in addition, some cool new titration tricks.
Opus then used those brush movements to compose and paint “leeward”, an autumn tree leaning into the wind.
nil retweeted
AI isn't just learning to see the world anymore. It's learning to leave its mark on it. Literally.
last night’s watercolor session with Claude! getting much better at trees now.
it also has a much bigger repertoire of brush strokes now, which enables it to compose drawings like this. and in addition, some cool new titration tricks.
Opus then used those brush movements to compose and paint “leeward”, an autumn tree leaning into the wind.
design pro tip: if you can't find a good font for your project, you can just ask your nearest agent to make one for you 🙃
nil retweeted
Today we’re launching the first AI modeling agency 💅 right inside Glif.
Cast hundreds of real AI models, drop your product, idea or brief and let Glif create super compelling content for you end to end.
If you still think AI models aren’t ready for real work, watch this 👇
🤖 Made with AI
there's stuff i'm doing with my robot arm, and then there's this...
Last night an AI agent performed brain surgery on a mouse.
We gave it 19 gene therapy vectors in a spreadsheet, a mouse model of epilepsy, access to a motorize surgery rig with cameras and one goal: reduce seizures.
It picked the drug. It picked the brain region. It derived the coordinates from three papers. Then it drove the stereotaxic arms into the brain and injected 250 nanolitres while watching the entry site through the rig camera for bleeding.
A licensed vet gated every irreversible step and held a physical kill switch to stop the AI agent.
Thread on what it decided, what it saw, and the moment it refused to let me override it.
[Writing this on the spot out of excitement, but I've been 18hrs in front of my laptop coding and coordinating this, so keeping it brief and descriptive, more cohesive thoughts on this soon...]
me: "hi, let's make a new fun painting"
Astra: comes up with the idea → models brush movements → creates a plan → digital twin tests for collisions → controls robot via SDK → starts camera recording via Sony's SDK → reads controller logs → downloads camera footage via WiFi → composes music → edits video to sync with controller logs and music spectrograph → sprinkles some hyperframe magic
1 hour later... "a Small orbit" is ready!
i know it's not really the same, but all the neuron editing and exploration posts of Qwen remind of this short story by qntm: qntm.org/lena
one reason i love painting as a long-term project for my robot + the agents operating it is,
- infinite depth in technique and finesse.
- infinite breadth in creations.
it’s an eval + a creative outlet + a growing body of work, all at once.
the arm has 7 dof and ±0.1mm repeatability. high-res cameras, top-grade brushes, paper and pigments, a well-calibrated indoor workspace. in principle, i think something of Hokusai's or Monet’s calibre is possible with this setup.
you can see the progression here, bottom to top: calibration runs and basic brush tests, then colour mixing, wet-in-wet, glazing, angled strokes...
just getting started! so much more to learn + create 🦾
nil retweeted
the crux of the "memory problem" is not how you store things (embeddings/markdowns) or how you retrieve. all memories are associative and depend on the task at hand. i bet task planning/decomposition and memory systems will morph together.
my biggest frustrations with ai tools rn is their opaque memory systems.
chatgpt knows some things about me, claude remembers smth else, claude code has a different system, codex feels like a sprawling web of long-forgotten chats, and codebase docs + skills are yet another system.
i DO want these memories to be contextual and siloed. different models and harnesses have different strengths. i want their memories to reflect that.
but a few things that really bother me:
1. Opacity: how are memories created, curated, updated, and forgotten? i have almost no visibility into this.
2. Context rot: what random memories and old chats are seeping into the current context window?
3. Curation: no tools to curate memories. i'd like to have powerful tools to inspect, edit, prune, and shape these memories.