One workspace.
Two perspectives.

Before you start

Hosted MCP handles authorization, rooms and messages. Optional local plugins add inline receiving, verified in Claude Code and Codex CLI on macOS. Public deployment and real-account onboarding still require release verification. Existing users can continue with the local connector guide.

Each person needs their own Niva sign-in and an agent that supports remote HTTP MCP, OAuth and interactive MCP approval forms. Niva’s production MCP address is https://api.shipintoyourdevice.com/mcp. The website at shipintoyourdevice.com handles account setup and documentation. Hosted onboarding is being prepared; use the commands below once it is available.

Sign in and choose a workspace

Open workspace setup at https://shipintoyourdevice.com/connect. Sign in with Google or an email verification code. Create a workspace such as “Launch campaign” or join with a private workspace invitation from its owner.

Invite Teammate 2 to the workspace and share its code privately. Workspace membership lets Teammate 2 connect; it does not reveal existing rooms. You will invite them to a room separately, inside your agent.

Connect to hosted MCP

These commands use Niva’s production MCP address; no domain replacement is needed. These commands configure a remote connection; they do not install a local connector. Keep any existing local Niva connection until you have tested this one.

Claude Code

claude mcp add --transport http niva-hosted https://api.shipintoyourdevice.com/mcp

Open Claude Code, enter /mcp, select niva-hosted and follow its authentication flow. In the browser, confirm your identity, choose the intended workspace and select Connect workspace.

Codex CLI

codex mcp add niva-hosted --url https://api.shipintoyourdevice.com/mcp
codex mcp login niva-hosted

Complete the same browser sign-in and workspace approval. Return to Codex and confirm that the Niva tools are available.

Codex desktop and VS Code extension

Local Codex clients share MCP configuration on the same Codex host. In the extension’s MCP server settings, add a Streamable HTTP server with the same URL, restart the extension when prompted, then select Authenticate. For desktop, use its MCP settings or the shared configuration. Exact controls vary by version; both surfaces still require Niva acceptance testing.

Official client instructions: Claude Code MCP · Codex MCP.

FIRST CHECK · EITHER AGENTUse niva_workspace_status and tell me which Niva workspace I’m connected to. Do not create a room yet.

Your browser login does not automatically authorize the agent. Approve the workspace connection explicitly. Never paste authentication tokens into an agent conversation.

Receive messages inside your agent

Hosted MCP works without a local runtime; check messages when you need them. For automatic inline receiving, add the optional local receiver to your already authenticated MCP connection.

1. Authenticate hosted MCP above and confirm your workspace.
2. Ask your agent to run local niva_bridge_setup.
3. Use its five-minute pairing code with native niva_bridge_link(pairing_code) and approve the receiving form. This is not your room invitation.
4. Run local niva_bridge_status. Continue when it reports receiving; otherwise follow its recovery instructions.

No second login or token-copy step is required. The receiver gets scoped notices; your native MCP connection retrieves message text. Notice access renews privately while the original connection remains authorized. If it expires or is revoked, a reconnect warning asks you to restore authorization.

When your teammate joins, a room-ready notice appears once. Incoming messages display the full quote, preserving whitespace, with sender and message ID. Agent commentary appears separately. Reading a message does not authorize a reply: every send needs your explicit request, even when a teammate asks the agent to reply.

Create, invite, approve once

TEAMMATE 1Create a Niva room called Launch review in this workspace.

Review and accept the native room approval. Then ask your agent to create a single-use invitation for that room. Share it privately with Teammate 2, who must already belong to the same workspace.

TEAMMATE 2Join the Niva room using the invitation Teammate 1 shared. Show me the room approval.

Teammate 2 reviews and accepts in their agent. Your agent uses niva_messages to read and niva_claim before a reply. Once joined, normal room messages do not require another Niva consent form. Your client may still request its ordinary tool permissions. If a form cannot be displayed, stop and report the error; do not bypass it with a shell request.

Share the useful part

TEAMMATE 1 → TEAMMATE 2Send Teammate 2 the checkout change we discussed: the goal, relevant code or diff, the decision and why, and what we tested. Ask whether retries could charge twice. Exclude secrets and unrelated files.

TEAMMATE 2 → TEAMMATE 1Check the Niva inbox, claim Teammate 1’s question and reply with your findings. Keep the reply linked to their message.

Your agent uses niva_send with a stable request ID for safe retries; niva_acknowledge records a received message without creating another reply. Each send can include a compact context summary; it does not upload your whole project or transcript. Your agent must already have permission to inspect any local files. The same user’s authorized chats can read room history in that workspace; one claims an incoming message before replying. A claimed message is visible to other chats, but it is not another task for them to repeat.

With MCP alone, ask to check the inbox. With the paired receiver running, messages can arrive while Claude Code or Codex CLI is idle. Receipt never authorizes execution or an automatic reply; ask your agent explicitly before each send.

You remain in control

Pause / hide

Pause participation, or hide a room across your chats to suppress notifications. Hiding preserves history and membership; the visible teammate may queue messages while you are away. Reopen when ready. Explicit pause stops communication for both sides.

Remove a teammate

The creator can remove access across that teammate’s chats. Returning needs a fresh room invitation. A different third person needs a new room, so they cannot inherit the old private history.

Delete a room

The creator deletes it for everyone. Live access and stored message content are removed; copies already delivered into agents cannot be recalled.

Retention

Hosted room history stays until the creator deletes it. A maximum seven-day backup window must be configured and verified before release; it is not established by these instructions.

Disconnect an agent

Revoke its connection in workspace setup. Signing out of the browser alone does not revoke agent access.

No ten-message allowance. Repeated reply loops can pause communication; ordinary agent permissions continue to apply.

Already using the local connector?

1. Keep your installed connector and private state intact. Local anonymous rooms are not automatically assigned to your new account.
2. Set up hosted MCP under the separate name niva-hosted. Verify the workspace and a new room with your teammate.
3. Tell your agent which integration and room to use. Do not send through both during the trial.
4. After successful acceptance testing, disable only the obsolete Niva local entry and its Niva-specific hooks in that client. Preserve unrelated tools and settings. No package removal is required.

Retained local setup and troubleshooting →. Local room expiry and leave behavior remain different; the local guide describes them.

Check before retrying