ottilves
Joined 12 years ago
Karma
11
Submissions
10
Member since
Sep 30
Recent submissions
Comment · 4 months ago
Comment · 4 months ago
Thank you!
As mentioned in another comment, I believe that an agent-neutral surface needs to exist for agent produced knowledge work, and even more importantly so if everyone in your org needs to have access.
Knowledge work shouldn’t have vendor lock-in, since the best model tends to change every two months, people use multiple agents, and not everyone in your org has a license.
Comment · 4 months ago
Thanks!
Versioned docs are already supported - each publish saves a new version with the previous ones remaining accessible. Diffs are coming too.
I think the co-editing/collaboration is very interesting. We currently support comments by anyone in your org with agents editing and resolving based on them (importantly, keeping the identity on whose behalf they’re acting intact).
I think all major platforms will add some sort of artifact sharing (case in point Anthropic today).
Where we differ is in thinking that agent knowledge work needs to be on a neutral surface, never vendor locked, and accessible to everyone in your org, regardless of whether they hold a certain vendor’s license. Hence our take on flat org-based pricing (no per seat) in the paid tiers.
Comment · 4 months ago
We build display.dev — a tool that publishes HTML and Markdown behind company auth (Google/MS SSO out of the box, in-line comments for collaboration).
Indigo Engineering (data tools for progressive organizers) was sharing AI-generated artifacts in Slack. HTML artifacts had to be pasted as screenshots since Slack can't render them. Comments lived in the thread, not on the work. Versioning was a mess.
They moved to display.dev. Their CEO Max Wood: "Before display.dev, we were sharing artifact files with each other in Slack and putting our comments there. For HTML artifacts, this meant a bunch of messy and often confusing screenshots. It also meant several conversations were mushed into the same thread, versioning was a nightmare."
Two unexpected wins: faster iteration on a major redesign they'd been mired in, and dropping Google Docs (their docs are now markdown-native, and converting them was a chore).
Full case study: https://display.dev/customers/indigo-engineering
It’s certainly a convenient default for heavy Claude users.
For multi-agent users, orgs that don’t have licenses for everyone in their org, orgs that don’t want to stay vendor locked, a neutral surface is still required.
That’s something I certainly still believe - agent agnostic surfaces are necessary for knowledge work.