Testing AI tools. Exploring onchain. Figuring out what grows on X. Sharing experiments, useful finds & honest results
Joined May 2024
- Tweets231
- Following31
- Followers8
- Likes22
Fiks retweeted
new skill: create-canvas.
last week I made a skill to put every component from a repo on one canvas. I started using it with my agent to create variations, compare ideas, and iterate visually without leaving the codebase.
so I made a new skill around that workflow.
instead of moving your work into another tool, bring the canvas into your codebase and use it to explore UI with your agent, using the real components, styles, and project context already there.
Fiks retweeted
Introducing Eleven Realtime, a new class of Speech to Speech models.
Voice agents usually make you choose between quick replies or precise answers.
Eleven Realtime gives you both. It starts talking in half a second and gets spoken reasoning questions right.
Fiks retweeted
We're making Shopify's mobile apps self-healing.
Agents watch production 24x7 for new crashes, reproduce them, write and verify a fix, then generate a short video explaining the root cause and the fix. Much faster to digest than the usual wall of text.
An engineer then just reviews and ships it.
Fiks retweeted
a weird thing about OSS pull requests these days is we don't know what model was used for it and our internal setup provides better tools to the agent
so they're almost always worse than sending the prompt ourselves
it's mostly useful for environments we cannot recreate
Fiks retweeted
This is Pele, my new rendering library for diagrams and charts, compatible with the latest Mermaid syntax.
- 100-500× faster than mermaid.js
- 6× smaller bundle
- No dependencies
- Easy to theme
- Responsive to device width
In pursuit of making Obsidian insanely fast and cohesively designed, I always found the Mermaid library to be too big, too slow, and too hard to theme. Pele will be the new renderer in the next version of Obsidian, but you can start using it now.
Pele [ˈpɛlɛ] is named after the goddess of volcanoes and fire. It's open source under the MIT license. Try the playground!
Fiks retweeted
From 𝟭𝟭 𝗺𝗶𝗻𝘂𝘁𝗲𝘀 down to 𝟳𝟮 𝘀𝗲𝗰𝗼𝗻𝗱𝘀.
A new ComfyUI node just cracked real-time speed for 𝗠𝗶𝗻𝗶𝗠𝗮𝘅 𝗛𝟯 character video generation.
𝗖𝗼𝗺𝗳𝘆𝗨𝗜-𝗥𝗲𝗳𝟮𝗩𝗔-𝗩𝗦𝗔 achieves a massive 𝟵𝘅 𝘀𝗽𝗲𝗲𝗱𝘂𝗽 using sparse attention DiT:
• 𝟳𝟮𝘀 𝘄𝗮𝗹𝗹 𝘁𝗶𝗺𝗲: Full 5.16s video @ 24fps (124 frames, 1344×768)
• 𝟭𝟯.𝟱 𝗚𝗕 𝗣𝗲𝗮𝗸 𝗩𝗥𝗔𝗠: Down from ~22.5 GB (runs on 16GB GPUs)
• 𝟰-𝗦𝘁𝗲𝗽 𝗦𝗮𝗺𝗽𝗹𝗶𝗻𝗴: Euler/simple sampler with 75% video sparsity
• 𝗭𝗲𝗿𝗼 𝗙𝗮𝗰𝗲 𝗗𝗿𝗶𝗳𝘁: Reference tokens stay locked out of attention pruning to maintain 100% character identity
Benchmark comparison on RTX 4090: → Native Dense H3: ~650s (~11 min)
→ Video Delta Net (VDN): ~135s
→ Ref2VA VSA: ~72s
Open-source on GitHub:
github.com/Kablex/ComfyUI-Re…
Fiks retweeted
Liquid Glass, for the web. Open source.
Apple's Liquid Glass look anywhere: Chromium browsers, Safari, Firefox, Electron etc.
It's early and it has rough edges. It runs great on desktop Chromium (that's what this video is). Safari and mobile are rough for now, and that's what I'm working on next.
npm i @glass-sdk/liquid-glass
Demo: liquid-glass.glassapp.dev
Repo: github.com/Glass-HQ/liquid-g…
Fiks retweeted
A few people asked how I made the isometric objects and cities, so I packaged it into a Claude skill.
Describe an object, device or building, and ISO-GLOW creates a single interactive HTML file.
Try it out yourself!
isoglow.dev
Fiks retweeted
something I have been thinking about is a way to approximate how well you’ve setup your codebase for agents. think of it as a thought experiment and rough heuristic, not a real number that can be compared
it’s not a fully formed idea yet, but i think there’s something to the idea of “time to (fully automated, hands off) rewrite” or ttr
as a thought experiment, lets say you decided to rewrite your code in a different language/framework/architecture. how long would it take a single engineer to do it?
the number itself isn’t that important, but it leads you to more questions that can help you directionally figure out how to make your codebase more legible and productive for agents.
for example, maybe you think your ttr is high because you wouldn’t trust the final result - because your agents don’t have a way to verify their work and convince you that their output is identical in user visible behavior to the original. well, that inability is likely also a problem today and slows you and your agents down
there’s also a more subtle question of the quality of the rewrite that would be produced. is perf better, the same, or regressed? is the code easy to delete and extend? and how much do you trust the rewritten version to be able to maintain its quality over time as PRs start flowing into it?
what do you think?
Fiks retweeted
I don’t think people appreciate how amazing the work @mxstbr & team is doing at OpenAI for MCP adoption
In the past month they’ve:
- supported skills over MCP
- supported MCP events
- dramatically reduced the friction adding third party MCP servers
- overhauled the submission flow
- implemented a novel really cool extension approach for embedding MCPs inside of ChatGPT
Is so incredible to see a push like this, candidly I thought it’d take forever to see skills over MCP and events supported but they’re doing it
Fiks retweeted
Claude now works inside Google Docs, Sheets, and Slides, and those files also open inside Claude.
In Google Workspace, Claude sits in a sidebar next to your file, reads what you have open, and edits it in place. You can approve each edit before it lands.
Fiks retweeted
Agents are getting complex to manage: models, skills, automations, permissions, cloud environments, orchestration patterns...
So, we built the Terraform for agents: one repository that configures all of your agents as code.
The Warp Factories configuration spec defines:
- Agents and orchestration: how work gets routed and which models agents use
- Automations: the events and schedules that kick off work
- Access and environments: repositories, secrets, MCP servers, and runners
- Measurement: scorers and benchmarks for understanding and improving performance
Because it’s all code, both engineers and agents can propose changes to the factory itself. That makes it possible to test new configurations, benchmark them, and even have your factory propose improvements as PRs.