Everyone on your team can now join kenno, no GitHub account needed.
kenno is where a team plans a feature together, and each engineer's own agent builds from that plan.
Until last week, you could only get in with GitHub. Fine for engineers, but it left out product, design, marketing and sales.
Now you can sign in with Google or an email code.
Invite your teammates by email and pick their role. They get an email, sign in, and land right in the plan.
Coding agents still connect through GitHub, same as before.
A bunch of product decisions get made on calls.
They live in someone's notes and the agents building it never see them.
Now kenno connects to @meetgranola so the call goes into the plan.
- Type /meeting in the chat
- Pick the call from Granola
- kenno proposes changes
- Apply the ones you agree with
Then every agent builds from the updated plan, with the shared context and decisions.
Jason Fried recently showed a writing tool he'd wanted for years.
A word, a sentence or a paragraph can have alternatives. You flip between them as you write.
We loved it.
And we thought it could be even more useful for teams and their agents planning together.
That's block versions in kenno.
Anyone on the team can write their version of a paragraph in the plan.
Their coding agent can suggest one too. Nobody's text gets overwritten.
- Add yours with ⌘⌥V
- See every option in one place
- Talk it through
- Swap in the one you agree on
When people see a decision differently, it's the easiest way we've found to align.
Agents can do all of this through kenno's MCP.
Add a version, read every version, swap one in.
When the build starts, everyone's aligned.
Every agent builds from the version in the plan.
For years, maybe a decade, I've wanted to build a writing tool that just did a few things I couldn't find anywhere else.
A system that mimicked how I think when I write. A system that provided clear affordances, features, and places to do the things I wanted to do. A way to play with my writing as I'm writing it. A way to settle into just the right way to say something.
It never made sense to make it a 37signals product because it's not commercially viable, nor would it be worth pulling people off their other work to hack on this. Plus, it would have taken months the old way.
So this weekend I just made it myself, with Claude's help.
It's called Write_On and the short video walks you through it.
Essentially it's "alternative control" at the word, sentence, and paragraph level, plus a way to dim stuff back, and stash stuff near by. Not version control, but alternative control. You'll see what I mean when you watch the video below.
So here it is. Write_On.