One project · one agent · everyone in the room

promptwithme

promptwith turns Claude Code or Codex CLI into a shared room. You pick a goal, invite whoever you want, and everyone prompts the same agent in the same project. No installs for them, no screen share, no losing the thread.

Desktop app for macOS and Windows, or npx promptwith. Free on your own machine; cloud containers from $12/month.

How it works

Three steps, and the second one is where you choose whether your laptop is involved at all.

01

Set the goal

Name the session, write what you are trying to get done, and drop in a task list. The agent gets that brief with the first prompt, so it starts pointed the right way.

02

Attach a workspace

Pick a folder with the desktop app's file picker, type a path in the browser, or upload the project to a container we run. Either way the agent is confined to that one workspace.

03

Share the link

Collaborators open it and start prompting. Everyone sees the same replies, the same tool activity, and the same checklist ticking down.

The agent stays in its box

Handing people a link to an agent on your computer is only reasonable if the agent cannot wander. Three layers keep it there.

Directory validation

/, /etc and your home directory are rejected outright, and paths are resolved through symlinks before anything runs.

OS sandbox

bubblewrap on Linux, seatbelt on macOS: the filesystem is read-only apart from the workspace, and credential directories are masked out entirely.

Agent permissions

Codex runs workspace-write with no extra roots. Claude runs with generated deny rules for system paths, secrets, and privilege escalation.

Two ways to run it on your machine

Same server, same rooms, same containment. Pick whichever start you prefer.

Desktop app

macOS and Windows. Launch it, click Browse… to choose the project folder, pick the agent it found on your machine, and the room opens in the window.

Download →

One command

Already living in a terminal? npx promptwith starts the same server and opens the same UI in your browser — nothing to install permanently.

Either way, a link

Sessions are just URLs. Collaborators open one in any browser: no account, no CLI, no access to your shell.

Sessions sleep, and wake up somewhere new

A cloud session does not run forever, and it does not vanish the second you stop typing. It has three states, and you can see all of them from your dashboard.

Active

The container is running and the link works. Anyone with it can prompt the agent.

Asleep

Idle past your plan's window, so the container is stopped and you stop paying for compute — but the workspace is untouched. The old link stops working the moment it sleeps. Waking it from the dashboard restarts the container and issues a new URL, so a link you pasted in a group chat last week cannot quietly bring the session back.

Ended

You terminated it, or it sat asleep past the retention window on your plan. The container and the uploaded workspace are deleted. This one cannot be woken — start a fresh session.

Ready when you are

Start on your own machine for nothing. Move to a container when you want the session to outlive your laptop lid.