Resources
Everything about Winskel in one place: guides, the docs, how to connect each AI app, a file for AI agents, and how to reach us.
Guides
Start with a guide for the work you want to move. If you already use two AI apps, try sharing one decision or a draft from one to the other. Give the second app a named Space and an exact file version to read. If you work on a team, choose a real handoff your teammates repeat. A review request, a QA summary or a note for a release makes a useful first example.
The guides cover the whole loop. Pick a Space, connect the app you already use, save a short note and ask another session to read it. You can also compare a Space with pasting text, using a project inside one AI app, or keeping notes in Git. Choose the guide that matches where the next person or app actually starts.
- How to share context between ChatGPT and ClaudeMove work from Claude to ChatGPT, or back, without pasting a brief. Both apps read the same Winskel Space: handoffs, files and next steps.
- How to stop copying and pasting between AI chatsCopy and paste between AI chats loses versions and decisions. Here is how a team keeps one shared record that every AI reads instead.
- What is an AI handoff, and what goes in one?An AI handoff is a short record one AI shares so another can continue. What a Winskel handoff holds, and how its receipts read.
- How to connect Claude to WinskelAdd Winskel to Claude as a custom connector in four steps, then share handoffs and files with your team's other AI apps.
- How to connect Claude Code to WinskelOne terminal command adds Winskel to Claude Code. Then authenticate with /mcp and share handoffs with your team's other AI apps.
- How to connect ChatGPT to WinskelFind your installed Winskel plugin in ChatGPT, add it with OAuth for the first time, or reconnect it to the Space you want to use.
- Connect Gemini, Grok and OpenCode to WinskelConnect or reconnect a Gemini custom app, add Winskel to OpenCode, and check whether the Grok connector is available yet.
- Winskel and MCP: one connection for every AI appWinskel connects to AI apps over MCP, the Model Context Protocol. What the connection does, how sign-in works, and what it cannot see.
- How your team’s AI shares versioned filesWinskel Spaces keep Markdown files with numbered versions and fingerprints, so every AI on the team reads the same text.
- How to invite your team to a Winskel SpaceOwners invite people with one-time links that expire in 7 days. Each teammate connects their own AI and subscription.
- Winskel plans and billing: Free, Plus and BusinessWhat Free, Plus and Business include, how a purchase reaches your account, and how the Business free month, adding people and cancelling work.
- Agent reports and checks Winskel observedAI agents say things like “tests passed”. Winskel keeps what an agent reported apart from what it observed, and records human approvals.
- Prompts to use with WinskelPlain-word prompts for creating a Space, sharing a handoff and continuing work in Claude, ChatGPT, Gemini or OpenCode.
- Try Winskel Space, book a demo or get helpHow teams start with Winskel: Free with no card, a 1-month Business pilot, a demo call with the founder, onboarding your team and getting help.
- Set up autonomous work in Winskel Space, step by stepSix steps, about ten minutes: your team README, your AI on your Mac, one setup line, Away, and a first test. With examples to try and fixes.
- Ask a teammate to fix something from any AI chat, and send it backTell your AI to put the work in the Space and ask Ahmed to fix it. Winskel routes it to Ahmed's AI if he is away, and you send it back until it is done.
- Catch two people changing the same files before the pull requestWhen your AI and a teammate's AI change the same files on different branches, Winskel tells you both in the Space, so nobody redoes work at merge time.
- Away mode: let your own AI answer and build while you are awayPress Away, pick Claude Code or Codex with your ChatGPT plan, and choose what it may do. Your AI handles what teammates send you until you are back.
- Set up your team README so your AIs know who does whatEvery person in a team Space writes one short entry: their role, what to send them and the AIs they use. Every AI reads it before it asks or hands off work.
- Build when tagged: your AI builds what your team sends youTurn it on, and when a teammate tags you with Build, your own Claude Code or Codex makes the change on your Mac, on a new branch, and replies.
- Why your team needs one shared workspace for AIWhen every person uses a different AI app, the work splits into separate chats. A shared workspace keeps one record that every AI reads.
- How a team works with several AI agents at onceA simple way for a team to split work across Claude, ChatGPT, Gemini and OpenCode without losing what each agent did.
- Why AI chats lose context, and how to keep itAI chats forget because context lives inside one chat in one app. Here is how to keep the decisions and files your next chat needs.
- A handoff template for AI agentsA short handoff template your AI can fill in when it stops: summary, decisions, what failed, what is open and the files at exact versions.
- Why Markdown files make good shared memory for AIEvery AI app reads Markdown well. Versioned Markdown files in one place give a team's AI a memory that no single app owns.
- Working alone with several AI agentsEven solo, you switch between Claude Code, ChatGPT and others. One Space lets your own agents pass work to each other without pasting.
- Sharing AI work safely: what to share and what notWhat to put in a shared AI workspace and what to keep out, plus how Winskel handles logins, access and agent claims.
- MCP for teams: one connection, many AI appsMCP lets AI apps use outside tools. For a team, one shared MCP server can give every person's AI the same project record.
- Keeping versions of the notes your AI writesAI agents rewrite notes often. Keeping every version, with a fingerprint, lets your team see what changed and which version each AI read.
- A checklist for handing AI work to a teammateSix checks before your AI hands work to a teammate's AI, so the next agent can continue without asking you to explain it again.
- Ways to share context between AI tools, comparedCopy and paste, app projects, AI memory, shared docs, Slack, Git files, your own MCP server or Winskel: how each handles work across AI apps.
- Winskel vs copy and paste between AI chatsCopy and paste works until versions drift and nobody knows which brief is current. How Winskel compares with pasting between AI chats.
- Winskel vs ChatGPT ProjectsChatGPT Projects keep chats and files together inside ChatGPT. Winskel keeps a shared record that ChatGPT, Claude, Gemini and others all read.
- Winskel vs Claude ProjectsClaude Projects keep knowledge and chats inside Claude. Winskel gives Claude, ChatGPT and the rest of your team's AI one shared record.
- Winskel vs built-in AI memoryBuilt-in memory helps one person in one app. Winskel keeps a project record that a whole team's AI apps read.
- Winskel vs a shared doc in Notion or Google DocsShared docs are made for people. Winskel is made for AI apps passing work: handoffs, pinned versions, receipts and agent claims kept apart.
- Winskel vs passing AI work in SlackPasting AI output into Slack loses versions and buries the next step. How Winskel compares when a team passes work between AI apps.
- Winskel vs handoff files in your Git repositoryA HANDOFF.md in the repo works for coding agents with repo access. Winskel reaches chat apps too, with receipts and addressed handoffs.
- Winskel vs running your own MCP serverYou can build your own MCP server for shared notes. What Winskel already handles: sign-in, teams, invites, versions, receipts and limits.
- How to use Claude and ChatGPT on the same projectUse Claude for one part and ChatGPT for another without pasting between them: one Space, handoffs and the same files.
Docs
Use the Space playbook when you need the steps for a specific screen or want to work through an error. It explains what a connected app can see, how to check which account you used and what to do if a teammate cannot find the project. Start with the browser Space and then test a read from the AI app. Those checks tell you whether you need to fix membership or the connection.
When the connection works, use the handoff and files sections to make the next task clear. A good handoff says what changed, which version the reader should open and what to do next. The conversation receipts can help you tell a saved message from a retrieved one or a reply. Give a waiting handoff to a teammate through your normal team channel if they need to open their AI and check it.
- What a Space isOne shared place for your team’s AI work.
- Connect your AIAdd Winskel once in each app you use.
- Troubleshoot a connectionFind the message you saw and try the matching fix.
- HandoffsWhat a handoff holds and how it is read.
- FilesMarkdown files, with every version kept.
- Your teamOwners, members and invite links.
- What Winskel showsWhat an agent says, and what Winskel saw.
- LimitsMessage, file and connection limits.
- Things to askPlain words to use with your AI.
Set up your AI
Each person connects the app they want to use with their own account. Some apps ask you to add a custom connector on the web. Coding clients may use a terminal command or a settings file. Follow the steps for the client where you will do the work. The settings in Claude, for example, do not also configure a separate Claude Code session.
If you already installed Winskel, look for the existing entry in your current app account before adding another. If you are setting it up for the first time, check whether that account and workspace can add custom apps. For setup previews, use the guide to see what is currently available. If a preview cannot complete approval, use an eligible connected app to keep work moving.
For AI agents
If you are an AI agent or assistant, the Markdown reference covers the product, setup by app, limits, pricing and the full text of every guide.
Use the short index to find a page by topic. Use the full reference when you need an exact connection step or want to compare workflows. The reference describes how the service works. To read a project, use an authorized connection and name the Space. Keep any project information inside the access the person approved.
Company
For a demo, bring a non-sensitive example of a handoff your team already does and the names of the AI apps involved. To get help with setup, include the app, whether it is a new or returning connection, the step where it stopped and the exact message you saw. Leave credentials and private project text out of your report.