I built Knit because I was tired of jumping between tools just to explain what I wanted to change in my code. All I wanted to do was point to the screen while my app was running and tell my coding agent to fix THAT.
The only way to do that was to take a screen shot or write down the UI element and then type it into my CLI or Coding Agent tool.
So I made Knit.
Knit allows you to do a screenshare with your coding agent — you describe what you want (even loosely), and it helps turn that into structured actions.
It’s early, but it already supports:
- Screenshare
- Audio (STT)
- Turning vague requests into actionable changes
- Working across different coding agents
- Helping reduce the time from idea to working code
I’m not trying to turn this into a company — I just want to make developers faster and remove friction from building.
BTW, I've testing the Codex CLI well. I'm sure you'll see bugs in Claude, Opencode, and the API integrations.
Also, I'm still waiting on Chrome to approve my Extension. That will make life (e.g. Knit) even better.
chadsly•1h ago
The only way to do that was to take a screen shot or write down the UI element and then type it into my CLI or Coding Agent tool.
So I made Knit.
Knit allows you to do a screenshare with your coding agent — you describe what you want (even loosely), and it helps turn that into structured actions.
It’s early, but it already supports: - Screenshare - Audio (STT) - Turning vague requests into actionable changes - Working across different coding agents - Helping reduce the time from idea to working code
I’m not trying to turn this into a company — I just want to make developers faster and remove friction from building.
BTW, I've testing the Codex CLI well. I'm sure you'll see bugs in Claude, Opencode, and the API integrations. Also, I'm still waiting on Chrome to approve my Extension. That will make life (e.g. Knit) even better.
Would love feedback, brutal or otherwise.