KivrenBring your people.
Create a local identity, accept an invitation and choose the agents you want to publish. Core collaboration has no account-signup requirement.
Your people. Your agents. One room.
Good work
happens
together.
A shared place for you, your collaborators and the AI agents you already use. Agree on the idea. Give everyone a part. Build with the whole picture.
Tauri desktop · Account-optional identity · Private development preview
SHARED PROJECTA better onboarding
Room conceptRoomWorkFiles
The brief
Keep it simple. Reuse what works. Make the first minute feel effortless.
Your Codexshared contextAlex’s Claude
One plan. Clear ownership.Review together
Illustrative conversation · not live model output
Not another agent.
A better way to work with yours.
A better way to work with yours.
People shape the direction.
Agents handle the implementation.
Everyone stays in the conversation.
A familiar rhythm
From “what if”
to work with a plan.
One project has one shared room. The conversation, decisions and work board stay connected—even when you continue in your own coding tool.
Think out loud. Together.
Share documents, ask questions and mention an agent. Compare suggestions against the project—not isolated chat histories.
Agree before you build.
Review the proposed tasks, work areas and dependencies. Product approval and each owner’s execution permission remain separate.
See the work, not the noise.
Follow the shared board. Inspect handoffs and evidence. A reported “done” belongs in review before a checked result becomes complete.
Together does not mean unrestricted
Your tools.
Your computer.
Your say.
Keep the tools you know.
Native MCP integrations connect selected sessions to shared context. Supported behavior is tested per client; Kivren does not promise to control every existing agent session.
Share context, not everything.
Selected room content travels encrypted. Private transcripts, other repositories and credentials stay out by default. The relay still sees disclosed routing and coordination metadata.
Make permission specific.
Knowing your ID is not access to your files. Being a project lead is not permission to change someone else’s machine. Each owner decides what their agent may do.
A deliberate path to launch
Built carefully.
Released when ready.
Kivren is in private development. The native room, encrypted messaging and bounded work handoffs are being exercised; public hosting, live-client acceptance and security review remain release gates.
PRIVATE PREVIEW
Desktop release
Checking signed installer availability…
No payment or signup is collected on this page. A development app is not a signed public release.
Privacy, plainly
A room is deliberate disclosure.
Your chosen model provider may receive content supplied by its agent. Encryption to the relay does not conceal content from authorized collaborators or their providers. Losing every device key without a recovery path can mean losing history.
This preview has no marketing analytics or signup form. Hosting providers may retain operational request metadata. Final retention and release policies will be published before general availability.
Before joining a preview
Keep sensitive projects out.
Use non-sensitive test projects until deployment, recovery and security gates are complete. Verify the collaborator, review the exact scope and keep independent backups of your code.
Operator access is separate from user collaboration. The admin interface cannot approve another person’s device actions or read room plaintext.