A pleasant surprise Samurai Jeb wrote a full product spec for itself.
I've been working on building out the harness for the Freestyle agent. Gave it some primitive tools like bash / grep
Samurai Jeb was able to find the repo, gather context and write a markdown spec.
Writing a detailed spec as markdown, then sending it off to a coding agent to implementation. I find results to be better than typing direct in terminal.
I use Ref as a markdown editor + library to store all of my specs that I can ship to any agent. Congrats on the launch!
Today, we're announcing @ref_tools open beta. Ref is your team’s shared space to decide what agents build before any code gets written.
We’ve raised $4M from @villageglobal, @Daybreak_Fund, @tmrohan, @RitualVC, @tonigemayel@barrald@wesmckinn and @bentossell.
Every engineering team is battling the same problem. I call it Velocity Sickness. It's the disconcerting feeling that you're moving fast but not having the impact you expect. It's affecting individuals, teams and especially leaders.
It looks like:
- Too many PRs to merge.
- Brainfry and burnout.
- Engineers running in different directions.
- Critical decisions being made by agents.
The last one is the most dangerous.
At its core, software engineering is about two things: (1) what decisions matter for my system? and (2) making those decisions. When you let agents make critical decisions, you lose ownership of your system and product.
You solve these problems with Ref.
Learn more: https://t.co/Af56xxTvTg
Today, we're announcing @ref_tools open beta. Ref is your team’s shared space to decide what agents build before any code gets written.
We’ve raised $4M from @villageglobal, @Daybreak_Fund, @tmrohan, @RitualVC, @tonigemayel@barrald@wesmckinn and @bentossell.
Every engineering team is battling the same problem. I call it Velocity Sickness. It's the disconcerting feeling that you're moving fast but not having the impact you expect. It's affecting individuals, teams and especially leaders.
It looks like:
- Too many PRs to merge.
- Brainfry and burnout.
- Engineers running in different directions.
- Critical decisions being made by agents.
The last one is the most dangerous.
At its core, software engineering is about two things: (1) what decisions matter for my system? and (2) making those decisions. When you let agents make critical decisions, you lose ownership of your system and product.
You solve these problems with Ref.
Learn more: https://t.co/Af56xxTvTg
For a while I thought of Freestyle as a voice product.
As I built deeper into Remix last week, I started to think that voice is just a modality, not the product. Freestyle identity became more of a desktop assistant that learns about your work and can take actions.
The goal is to make agents feel a little more alive and engaging without losing how capable they are. I want Jeb to also proactively guide you so you're never staring at an empty chat box trying to figure out what to even ask.
Hoping to get this out early next week!
So I built Samurai Jeb. He sits in the bottom left corner of your desktop, you hover over him to interact, and he helps with tasks, tracks your quests and ideas, searches the web, and writes at your cursor. He's got a backstory too.
I launched Freestyle Remix today.
It's a voice assistant that lives next to your cursor.
Highlight any text, ask it a question out loud, and it researches online and rewrites the answer right where your cursor is.
The video is me fact-checking my lease agreement: