Winy

Use case - Claude Code

Attach Winy to the Claude Code sessions you already run

Keep Claude Code in your terminal. Winy attaches to the sessions you already run and puts each one on your board as a live card, so nothing has to move.

You started Claude Code in a terminal, it is halfway through a task, and you want a better view of it: its choices as buttons, its conversation easy to read, your notes beside it, and a look at it from your iPad.

Claude Code's own desktop app does not pick up a session that is still open in another terminal; its docs say to close it there first. Winy works the other way round: your Claude Code sessions can still live in your terminal, and Winy attaches to the ones you already run.

How it works

  1. Keep running Claude Code

    Start Claude Code in whichever terminal you use, the way you do now.

  2. Your sessions show up

    Sessions you already have running show up in Winy, ready to put on the board.

  3. One tap puts it on the board

    Tap a session and it lands on your board as a live card, right next to your notes.

What the card gives you

Other ways to reach a running session

Claude Code has its own ways to reach a session from somewhere else, and each is the right pick for some jobs. If all you need is to answer one session from your phone, Remote Control is built in.

OptionWhat it doesYour terminal session
Remote Control (/rc)Continues a session running on your machine from claude.ai/code or the Claude app on iOS and Android; needs a Pro, Max, Team or Enterprise planKeeps running, and you can type from both sides
Agent View (claude agents)One screen listing your background sessions by state, to peek at or attach toShows up once you send it to the background with /bg
Claude Code Desktop (/desktop)Saves the session and opens it in Anthropic's desktop appThe CLI exits and the desktop app takes over
WinyAttaches to the session and puts it on your board as a live card, beside your notes, on Mac, iPad and iPhoneStays in your terminal; nothing has to move

Questions

Can I attach a GUI to a Claude Code session that is already running in my terminal?

Claude Code Desktop cannot: its docs say it does not move a session that is open in another terminal or still running in the background, and its /desktop command hands a session over by exiting the CLI. Remote Control lets claude.ai/code or the Claude app continue a running session. Winy attaches to the sessions you already run and shows each one on your board as a live card.

Do I have to restart my Claude Code session?

No. Winy attaches to the sessions you already run, so the session stays in your terminal and nothing has to move.

Does it work with any terminal?

Yes. Your Claude Code sessions can live in whichever terminal you use, and Winy attaches to the ones you already run.

Does attaching work with Codex or other agents?

Attaching, pickers as buttons and the conversation view are Claude Code extras. Codex and other command-line agents run on the board too, as real, live sessions in terminal cards.

How is this different from Remote Control?

Remote Control continues one local session from claude.ai/code or the Claude app, on a Pro, Max, Team or Enterprise plan. Winy puts each session you attach on one board as a card, next to your notes and ink, and that board opens on your Mac, iPad and iPhone.

Is Winy available yet?

Winy is in early access and coming soon to Mac, iPad and iPhone. Join the Slack community at winy.ai/slack for early access. There is no pricing yet.

Thinking is Winning

Think with your agents.

Winy is a Mac, iPad and iPhone canvas where you think and work with AI agents in one place. Better thinking in, better output.

Read next