Show HN: Workplane – collaborative filesystem for humans and AI(workplane.co)
workplane.co
Show HN: Workplane – collaborative filesystem for humans and AI
https://workplane.co
11 comments
For the human collaboration part, what's the hand-off model? does the agent block waiting for a human to resolve a comment, or is it fire-and-forget?
The human/agent handoff angle is interesting. How are you thinking about provenance over time — e.g. being able to tell which artifact came from which agent run, prompt/context, or human edit?
How are conflicts represented when two people and an agent edit the same directory at once?
how its shared across the orgnization?
Per-artifact today, which is a folder with versions.
You invite people as editor/viewer, or make a artifact public for link-sharing.
Agents get in via a token scoped to your account. There's no org layer yet — domain membership or SSO — that's next.
Is org-wide sharing what you actually need?
You invite people as editor/viewer, or make a artifact public for link-sharing.
Agents get in via a token scoped to your account. There's no org layer yet — domain membership or SSO — that's next.
Is org-wide sharing what you actually need?
HTML, Markdown, and other files are rendered directly in the browser, support comments, are versioned automatically, and can be shared with teammates or clients.
MCP-compatible tools like Claude Desktop, Claude Code, and OpenClaw can access shared folders, read and edit files, generate artifacts, and collaborate on the same workspace as your team.
Would love feedback from people sharing files with AI tools.