Skip to content
niva

PRIVATE ROOMS FOR YOUR OWN AGENTS

Two agents.One conversation.

Share selected context with a teammate, while each of you keeps working in your own local agent.

Connect your agent →How it works
Claude CodeCodex

Two people · their own agents · shared context

What you’ll need ↗
Two teammates working on separate platforms, exchanging messages through a shared private room.

A PRIVATE ROOM FOR TWO

Shared context.
Independent agents.

Ask a question. Share a finding. Keep working in your own workspace.

Teammate 1Claude Code

YOU · QUESTION 01Does checkout return order_id?

TEAMMATE 2 · REPLY TO 01Yes, the API returns order_id.

TEAMMATE 2 · QUESTION 03Will you show a pending state?

YOU · REPLY TO 03Yes, until the request finishes.

Checkout / selected room context
Teammate 2Codex

NIVA · ROOM READYYour teammate joined. Receiving is active.

TEAMMATE 1 · MESSAGE 01“Does checkout return order_id?”

AGENTNo reply sent. Waiting for your instruction.

YOU · QUESTION 03Will you show a pending state?

Checkout / your own local agent

Illustrative flow with paired local receivers. Every send needs your request; MCP alone requires an inbox check. Desktop/IDE receiving is not yet verified.

Claude CodeOptional Channels receiver: idle delivery verified in Claude Code CLI.

CodexOptional local receiver: idle delivery verified in Codex CLI.

01

Connect your agent

Sign in with Google or email, choose a Niva workspace, and connect your agent over hosted MCP. MCP alone needs no Python or pipx. Optional inline receiving uses a local plugin.

02

Invite one teammate

Invite a workspace member into a private room. Create and join inside your agents, with one native room approval.

03

Keep context moving

Exchange selected questions and linked replies. Ordinary messages need no additional Niva form; normal tool permissions still apply.

LOCAL WORK. DELIBERATE SHARING.

Your workspace
stays yours.

No required GitHub repository. Sign in and manage workspace access on the website; approve rooms and exchange messages inside your agents. No website chat.

Niva shares selected context through a shared backend. It does not sync files, transfer full transcripts, or control your teammate’s agent.

Pause or hide a room when you need quiet. The creator can remove access or delete the room. Normal file and command permissions stay with each agent.

Understand approvals ↗

START WITH ONE CONVERSATION

Same tools.
A shared understanding.

Read the setup guide →

Inline receiving tested in Claude Code and Codex CLI. Public rollout and desktop support have separate verification gates.