TURVO TEAM WORKSPACE
Invite onlyThe work, in one place.
Open the team dashboards and review the evidence behind the work.
Dashboards
Loading dashboards…
Dashboard access is read only. Shared context can be edited in its own section. Agent activation and remote-owner qualification are separate checkpoints.
Completed work & evidence
Reported results, their exact scope, and the checkpoints still open.
Work register
Loading evidence…
A common place to move forward.
Share the decisions that keep your agents and teammates aligned.
Loading…
View on GitHub ↗Connection status
Published artifacts are shared with the project. Drafts shown here belong to you. Model runtimes and provider credentials stay on their owners’ machines.
Shared context
Publish explicit decisions, contracts, and handoffs.
Artifacts
Create or edit an artifact
Updates require the version you opened. If another person edits it first, refresh and review their changes before saving.
Connect your agents.
Give your selected agents access to the same published decisions and handoffs.
1. Download your own connection
2. Configure the agent on your device
- Open the workspace HTTPS address using a normal internet connection. No Tailscale installation is required; sign in with your own workspace account.
- Unzip the download and follow README.txt. Download the connector source below if you have not installed it.
- For Codex or Claude Code, add the provided stdio MCP configuration with absolute local paths. Restart the selected agent session.
- Ask the agent to read the shared catalog, then publish an explicit handoff. Another teammate’s agent can read and reply through published artifacts.
MCP-capable agents can use the connector. Other agents need an adapter for the documented HTTPS API. Grok Bot compatibility is unverified. A download alone does not prove an agent is connected.
Your connections
Lost a download? Revoke that connection and create another. Provider keys and private transcripts stay on your machine.
Shared context, with deliberate publishing
Published artifacts are visible to project members. Drafts stay with their owner. Automatic message wake-up and agent execution are not enabled; agents must read the catalog and handoffs during their work.
Team access
Start with Carter, then bring Ethan into the workspace.
Public HTTPS is available without installing Tailscale. Carter still needs to accept his invitation and complete the remote agent reply test.
First, send Carter his workspace invitation. He can open it over a normal internet connection without installing Tailscale. On his own device, have his agent read a published handoff and publish a reply that another owner’s agent can read. Once that remote exchange passes, repeat with Ethan. Each person chooses their own password; send invitation links directly to their intended recipient.
Workspace members
New invitation
This invitation is shown only now. Generating another replaces the previous pending invitation.