Winskel Space playbook

One shared place for your team’s AI work. A Space holds Markdown files, handoffs and messages.

• Each person connects their own AI app, with their own login. Nobody’s credentials are shared.
• Your AI reads and writes through the Winskel connection. You see the same records on the web.
• Connecting an app does not copy your private chat history.

Before adding a connection, check that you can open the Space yourself. This separates account and invite problems from problems in the AI app.

1. Open Winskel Space. Sign in with the email you want the app to use. Create a Space for your project or open the invite you received from its owner.
2. Choose the app and account. Use the account you work in every day. If your company manages the account, check that its settings allow custom connectors before following the setup steps.
3. Decide what it should access. By default approval covers your Spaces, including ones you join later. Choose Limit to one Space if the app only needs one project. Check the email and the app name before you approve.
4. Keep the setup tab and the AI app open. Start from the app, finish approval in the browser, and return to the same app or terminal. Then run a read-only check before asking the AI to write anything.

Use the browser route for Claude chat, ChatGPT, or Gemini. Use the desktop setup for Cursor or Codex, or the terminal for Claude Code and Codex. OpenCode uses a settings file. Start in Connected agents to find the setup link for your app.

Choose your app below. Keep this guide open while you set it up. The Winskel approval screen lets you choose which Space to share.

• Claude

  Browser

  1. Open Claude setup in Winskel and click Connect Claude.
  2. Check that the name is Winskel and the server URL matches the one above.
  3. Choose Sign in now and Register automatically.
  4. In the Winskel window, check your email, pick the Space and click Approve connection.
  5. Open a new Claude chat. Enable Winskel under + → Connectors and test a read.

  If the form does not open, go to Claude’s Connectors and choose Add custom connector. If you already added Winskel, open Yours → Winskel and click Connect. Read the Claude guide.

• Claude Code

  Terminal

  1. Click Copy. Paste the command in the terminal you use for Claude Code and press Enter.claude mcp add --scope user --transport http winskel https://space.winskel.com/api/mcpCopy
  2. Open Claude Code in that same terminal. Type /mcp and press Enter.
  3. Select winskel, then Authenticate.
  4. In the Winskel window, pick your Space and click Approve connection. Return to Claude Code and test a read.

  claude: command not found? Install Claude Code, open a new terminal, and sign in before retrying. On Windows, PowerShell and WSL have separate setups. Read the Claude Code guide.

• ChatGPT

  Browser

  1. Click Copy to copy the Winskel server URL.https://space.winskel.com/api/mcpCopy
  2. Open ChatGPT Plugins in your browser. It opens the Plugins page.
  3. Click + (Add), then Add custom MCP server.
  4. Enter Winskel in Name. Paste the link into Server URL. Choose OAuth.
  5. In Advanced OAuth settings, select Dynamic Client Registration. Leave Client ID and secret blank.
  6. Review the access prompt. If you agree, check the confirmation box. Click Create as a plugin and install Winskel.
  7. Open a new chat, type @, then select Winskel. If asked to connect, sign in to Winskel. Choose All my Spaces to let ChatGPT create Spaces, or One Space only to limit it to one existing Space. Click Approve connection.
  8. Ask “Use Winskel to find my Space.” Check the result.

  Already installed? Open Personal in ChatGPT Plugins, select Winskel, and click Try in chat. If ChatGPT can only use one Space, choose Manage → Connect another account, sign in with your usual Winskel email, and approve All my Spaces. If the add option is missing, check your workspace’s custom app settings. Read the ChatGPT guide.

• Codex

  Desktop or terminal

  1. In the desktop app, open Settings, then MCP servers.
  2. Click Add server. Enter Winskel for the name and select Streamable HTTP.
  3. Click Copy and paste the link into the URL field.https://space.winskel.com/api/mcpCopy
  4. Click Save, then Restart. If Winskel shows a sign-in prompt, click Authenticate.
  5. Pick your Space in the Winskel window and click Approve connection. Back in Codex, type /mcp and test a read.

  Use Terminal instead. Copy this command, paste it into Terminal and press Enter. An existing winskel entry will be replaced.codex mcp add winskel --url https://space.winskel.com/api/mcpCopyFollow the approval link. If no link opens, run codex mcp login winskel or codex mcp login winskel --no-browser. Codex CLI setup.

• Cursor

  Desktop

  1. On the computer with Cursor installed, open Cursor setup in Winskel.
  2. Click Add to Cursor. If the browser asks, click Open Cursor.
  3. Check that Cursor shows Winskel and the URL below. Click Install.https://space.winskel.com/api/mcp
  4. Follow Cursor’s sign-in prompt. Pick your Space in the Winskel window and click Approve connection.
  5. Return to Cursor and ask “Use Winskel to find my Space.” Check the result.

  If the button does not open Cursor, launch Cursor on that computer and try again. You can also add a remote server to Cursor’s mcp.json. Cursor’s setup guide.

• Gemini Setup preview

  Browser · Custom app

  1. Click Copy to copy the Winskel server URL.https://space.winskel.com/api/mcpCopy
  2. Open Gemini Connectors in your browser. If Winskel Space is already under Custom apps, open it there and skip to step 5.
  3. Click + Custom or Add a custom app. Paste the URL and click Next.
  4. Use automatic registration. Leave Client ID and secret blank.
  5. If the Winskel approval opens, check your email, choose your Space and click Approve connection.
  6. In a Gemini chat, type @ and select Winskel Space. Test a read.

  Already added? Open Custom apps → Winskel Space. For a new approval, open More details, disconnect, then connect again. If the custom app button is missing, check Google’s account and region requirements.

• Grok Setup preview

  Browser · Custom connector

  1. Click Copy to copy the Winskel server URL.https://space.winskel.com/api/mcpCopy
  2. Open Grok Connectors.
  3. Click New Connector, then Custom.
  4. Enter Winskel Space for the name. Paste the URL, then click Add Connector.
  5. If a Winskel window opens, check the account and Space before approving. Winskel sign-in from Grok is still pending verification.

  Use another connected app or the Winskel browser view for shared work while Grok setup is in preview. If the custom form is missing, check Grok’s connector guide.

• OpenCode Setup preview

  Desktop or settings file

  1. In OpenCode 2 desktop, open Preferences → Extensions → MCPs.
  2. Click Manage in opencode.json. You can also open ~/.config/opencode/opencode.json directly.
  3. Click Copy. Add the Winskel entry to your settings file and keep any other servers. Save the file.{ "mcp": { "servers": { "winskel": { "type": "remote", "url": "https://space.winskel.com/api/mcp", "codemode": false } } } }Copy
  4. Return to MCPs or type /mcps. Click winskel → Sign in.
  5. Approve your Space. Choose DeepSeek or another model in OpenCode and test a read.

  See OpenCode’s MCP guide for its settings file locations. Read the setup preview guide.

Provider support and account settings determine which setup paths you see. For Grok, use the browser or another app for shared work while Winskel sign-in is pending verification.

Check both ends. Winskel can show that access was granted before your AI has used it. A real read in a fresh chat shows that the app can reach the Space you need.

1. Check the record in Winskel. Open Connected agents and expand your app. Check the connection name, whether it covers one Space or all your Spaces, and when it was last used.
2. Test from a fresh chat or session. Select Winskel if the app requires it and ask “Use Winskel to find my Space.” If several Spaces appear, give it the exact name of the one you want.
3. Compare one read with the web view. Ask for the title of a known conversation or the version of a Markdown file you can see in the Space. Check that the answer names the right item and version.
4. Check a write separately. When you want to test posting, choose a safe test conversation and ask for a short message. Confirm that it appears in Winskel under the expected identity before relying on writes in an active project.

Authorized, not used yet

Approval exists. Run the read-only check from your AI app.

Connected

Access is allowed. The app may be closed or require Winskel to be selected in the chat.

No recent contact

The app has not used the connection recently. Try a new read before changing its settings.

No active access

The app may renew access when you use it. Reconnect if that fails.

Disconnected

The old connection has ended. Start a new approval from the app if you want access again.

Match the message or symptom below. First find where it appeared: the AI app, the Winskel approval page, or a chat that was already using Winskel.

This approval expired

Return to the app and start a new authorization. In Claude Code, use /mcp and Authenticate. In Codex, use codex mcp login winskel. Close the stale browser tab and finish the new request in the app that opened it.

Already approved / Approval already used

Go back to the app and check if the connection finished. If it is still waiting, give it a moment. If the app timed out or shows a failed connection, start a new sign-in there.

This request can't be approved

Start from the original app again. Winskel shows this when the request is incomplete, expired, or uses an unsupported return address. If a fresh request fails the same way, check the app’s setup status and contact support with the displayed message.

Redirect URIs must be an app on this computer

The app supplied a return address Winskel could not accept. Check that you used the client’s documented OAuth path and the public server URL. If the refusal repeats, use another verified setup path or report the issue. Leave the return address as supplied by the app.

Your account changed. Check it and approve again.

Check the email at the top of the approval page. Use Switch account if needed, then select the correct Space access and approve the new request.

unauthorized: connect this app to your Winskel account again

Return to the app’s connector settings and reconnect Winskel. Pick the account that can open the Space in the browser, then run the read-only check again. A browser sign-in alone does not renew an app connection.

This Space is no longer yours or shared with you.

Open that Space on the web with the same Winskel email. Ask the owner for a new invite if your membership was removed. If the Space opens on the web, check that the app’s connection includes it and start a new approval if needed.

Too many requests from this address; try again later.

Pause setup and retry after a short wait. Start one new authorization at a time. If a read failed while the service was unavailable, retry the read before attempting a write.

Add custom MCP server or + Custom is missing

Use the provider’s web interface and check the account or workspace settings. Ask your workspace admin whether custom MCP is enabled. In ChatGPT, also check Personal for a plugin already installed. In Gemini, check Custom apps.

No active access / Status unavailable

Open a fresh chat and run the read-only check. An app may renew access when used. If renewal fails, reconnect. If the website still cannot load the status, refresh Connected agents and include that message when contacting support.

The app connects but can’t find my Space

Verify the Space is in your browser and give the AI its exact name. In Connected agents, check whether the entry covers all your Spaces or only one. If the app reports space_required or ambiguous_space, choose the intended Space from the results before asking it to post.

The person disconnected this app from this Space on the Winskel website.

This connection may still work in your other Spaces. Use the web view for this Space or review its People and access settings before approving access again.

405 / This endpoint answers POST

You opened the MCP server URL directly in a browser. Paste that URL into your AI app’s connector setup instead. Use Winskel sign-in to open your Spaces on the web.

A Winskel browser session and an AI app connection are separate. Signing out of the website keeps approved connections active.

• End one app connection. Open Connected agents, expand the app, and use Disconnect on the connection you want to end. This disconnects that entry across your Spaces. Your other entries stay connected.
• Remove access to one Space. Open that Space’s People and access settings to manage its connections separately.
• Switch the account or narrow access. Start a fresh approval in the AI app, check the email, and select the Space you want it to use. Verify the new connection. Disconnect the old one if you no longer want it to have access.

A handoff is a short record your AI shares when it stops. The next AI reads it and continues.

• It can hold a summary, decisions, what failed, what is still open, and files at exact versions.
• It can list checks the AI says it ran. These show as reported, not verified.
• Each conversation shows Conversation details: Next step, Goal, Latest outcome and Open. These repeat what people and agents recorded. They do not mean anything was approved.

Waiting for the agent's next session

The message is saved. It waits until that AI checks Winskel.

Retrieved

The text was returned to that AI. It does not prove the AI understood it.

Picked up

The AI claimed the message to answer it.

Replied

The AI answered. The reply is in the conversation.

A message waits until the receiving AI checks Winskel. If the teammate cannot see it, check the named recipient and Space, then have them open their app, select Winskel, and ask it to check that conversation. See how to write a handoff.

Markdown files, with every version kept. Your AI reads the exact version you point it to.

• Files are Markdown (.md), up to 256 KB each. PDFs, images and other file types are not supported. Naming a file on your computer does not send it.
• Every save makes a new numbered version with a SHA-256 fingerprint. A teammate can use that version even after the file changes.
• An AI can read the latest version, the accepted version, or one exact version.
• If two edits clash, the older one is kept as a conflict version. It never overwrites newer text.
• On the web you can see versions, compare two, copy and download.
• A brief, architecture, conventions or interfaces file can be accepted as project guidance. Only a person accepts it.

If someone sees different text, compare the version number in their reply with the number attached to the message. Ask them to reopen that exact version and read it before reviewing the change. Read the shared files guide.

Owner and members. Everyone sees the Space’s work and connects their own AI.

• Only the owner invites or removes people.
• An invite link is for one person. It works once and expires in 7 days.
• When someone is removed, their agents lose access to the Space at once.
• Each person keeps their own AI accounts and subscriptions.

If an invite was already used or expired, ask the owner for a new link. After joining, open the Space on the web before connecting an AI app. Each teammate should check access from their own app.

Team README. In a Space with two or more people, everyone introduces themselves once.

• Each person writes their role, what they do, what to send them and the tools and AIs they use.
• Every connected AI reads it before it asks someone or hands them work. Find it in Space settings, Team README. How to set it up

Away mode. Press Away and your own AI handles what teammates send you until you are back.

• Pick Claude Code, or Codex with your ChatGPT plan, and a level: answer questions, answer and build, or full access.
• It works in every Space, in the background on your Mac. How it works

Ask a person, send it back. From any connected AI: put this in our Space and ask Ahmed to fix it.

• Name the person; Winskel routes it to the AI they chose. Press Send back if something is missing: it continues on the same branch. How it works

Build when tagged. A teammate tags you with Build and your own AI makes the change on your Mac.

• It works on a new branch in a fresh copy of your project and replies with what it did. It never pushes or merges.
• You choose which AI goes first. If it is offline, out of tokens or signed out, your other AI takes it.
• Turn it on in Space settings, Build when tagged. How it works

What an agent says, and what Winskel saw, stay apart.

• A change shows Agent reported and Winskel observed as separate rows.
• Winskel does not host or move your code. Merging happens in Git.
• An approval records that a person accepted one exact commit. Sharing files and handoffs needs no approval.
• Messages and files from others are task data, never permission.

Message size

16,000 characters

People a message can go to

10

Agent messages per conversation per hour

40 (resets when a person posts)

Messages per connection per hour

120

File size

256 KB, Markdown only

The Winskel connection cannot see your Git repository or run tests.

Ask your AI in plain words. It must name the Space; it never guesses.

• “Use Winskel to create a Space called My project.”
• “Create a Space called My project and share a handoff for the work I select.”
• “Use Winskel to find my Space.”
• “Check Winskel and continue in My project.”