Claude
Free & PremiumThe Claude tool window is your overview of Claude Code in the open project. You start Claude from here and see your plan limits and usage, the project's memory files and everything Claude knows: agents, hooks and plugins. The window only reads files and runs commands that involve no model. Nothing here costs tokens.
Claude Code itself runs in the editor's Terminal or, with several sessions at a glance, in Mission Control. The management part of the window is the same as WebDonkey's Claude page (WebDonkey: Claude), so it needs WebDonkey on this Mac.
What you do here
- Set up Claude Code, sign in and start it in the project: The window.
- Keep an eye on your plan limits, in the status bar too: The window.
- See what Claude used today and over the last days, which memory files it reads at every start and which plugins are installed: Usage, memory and plugins.
- Show Claude your open file and selection and review its edits as a diff: The IDE bridge.
- Put files and lines into Claude's prompt: Send a selection to Claude.
- Create and change agents, hooks and plugins: Premium part.
Layout of the window
- Header: the Claude Code version, your plan and the signed-in account, next to it Start Claude and the arrow Open the Claude page in WebDonkey.
- Sections: Limits, Usage, Memory and Agents start expanded, Hooks and Plugins collapsed. A click on a heading toggles it, and the editor remembers this per project.
- Window menu (⋯ at the top right): Refresh reads everything again and puts the sections back to how they started. It also holds the entries every tool window has, such as Open as tab and Open in own window.
Out of the box the window sits in the right stripe (icon ✳). ⌘3 opens it.
Free and Premium
The window, the limits, today's usage, the memory files and viewing agents, hooks and plugins are free. Premium adds the usage of the last 7 days, creating and changing agents, hooks and plugins, and opening Claude straight in Mission Control. The details are in the Premium part.
The window Free
The Claude window sets up Claude Code, starts it in the open project and shows what Claude knows there. Once everything is set up, the top shows the version and your account, below it your plan limits and the sections for usage, memory, agents, hooks and plugins.
Where to find it
- Click the ✳ icon in the right stripe or press ⌘3.
- Menu View › Tool Windows › Claude.
- A click on the limits in the status bar (for example "✳ 64 % · W 18 %") opens the window as well.
How to do it
Claude Code is not installed yet
The window shows the card Set up Claude Code with the steps Homebrew, Node.js and npm (MCP servers often run via npx), Claude Code and Available in the terminal. Anything already present is marked already there.
- Click Set up Claude Code.
- Wait until all steps are done (Setting up …). Nothing is installed twice.
Installed but not signed in
The window shows Almost done.
- Click Open terminal with claude.
claudestarts in the editor terminal. - Follow the sign-in in your browser.
- The window checks the sign-in by itself (Checking the login every 5 s …) and then shows its full content.
Start Claude
- Open a project in the editor.
- Click Start Claude in the window header or press ⌘⎋ (command Claude: Open the project's Claude terminal).
- If a Claude already runs in an editor terminal of the project, the editor brings that terminal to the front instead of starting a second one. Otherwise it opens a new terminal with
claudein the project folder.
With Premium, Start Claude can lead to Mission Control instead of the terminal. You set that under Settings › AI › Open Claude in (Premium part). If the cursor is already in a terminal, ⌘⎋ takes you back to the editor.
Continue the last conversation
The command Continue last Claude conversation (menu Tools or the command palette) brings back the latest Claude conversation of the project folders. The editor runs claude --resume in the folder the conversation belongs to.
Window header
| Element | Meaning |
|---|---|
| Claude Code and version | the installed version, followed by your plan |
| Account | the email address Claude Code is signed in with |
| Start Claude | starts Claude in the project (⌘⎋) |
| Arrow | Open the Claude page in WebDonkey: jumps to WebDonkey's Claude page |
When the window is narrow, Start Claude and the arrow move below the version.
Sections
| Section | Shows | At first |
|---|---|---|
| Limits | your 5-hour window, the week and a spend limit if your plan has one | expanded |
| Usage | tokens and approximate cost (Usage, memory and plugins) | expanded |
| Memory | the files Claude reads at every start in the project | expanded |
| Agents | the agents Claude knows | expanded |
| Hooks | commands Claude runs at fixed moments | collapsed |
| Plugins | Claude Code's installed plugins | collapsed |
A click on a heading expands or collapses the section. The editor remembers this per project.
Limits
Each bar shows how much of the limit is used and when it resets (resets with the time). Once that time has passed, it says reset. From 70 % the bar turns yellow, from 90 % red. Below it you see where the value comes from: which session and how old it is, or per /usage.
Claude Code reports its plan limits only to its statusline. So that WebDonkey and the editor see them, there is the statusline bridge:
- Click Show live limits (install statusline bridge). Your existing statusline keeps looking exactly the same.
- Type something in any Claude session. The limits appear with Claude's next statusline update.
While the bridge is active, it says Statusline bridge active. Remove takes it out again after a confirmation, and your previous statusline comes back. If you set another statusline yourself in the meantime, it says Your own statusline replaced the bridge.
The same numbers appear in the status bar at the bottom right: "✳ 64 % · W 18 %" means 64 % of the 5-hour window and 18 % of the week. From 80 % the value changes colour. A small dot in front of the ✳ shows that a Claude is connected to this editor through the IDE bridge.
Agents
Agents are specialists Claude hands work to, each with its own instructions, tools and model. The list shows every agent from your user folder, from projects and from plugins. For each you see name, description, the model (or inherits model), the tools (all tools or a number) and where it comes from. If there are none, it says No agents yet.
Creating, editing and deleting is Premium (Premium part).
Hooks
Hooks are commands Claude runs at fixed moments, for example before a tool, after an edit or when it waits for you. The list groups them by event and explains each event in one sentence. A hook that calls a model every time it fires carries the label costs tokens. If disableAllHooks is set in Claude's settings, a note says that none of the hooks run.
Above the list sits the switch Keep the WebDonkey agent up to date. When it is on, WebDonkey writes the agent webdonkey-cli with every wd command of the installed version to ~/.claude/agents/webdonkey-cli.md whenever a Claude session starts. The switch and creating or changing hooks are Premium.
Without WebDonkey
The management in the window comes from WebDonkey. If WebDonkey is not installed on this Mac, the window says Claude management comes with WebDonkey. The terminal works without it: type claude.
- If Claude Code is installed, Start Claude starts it in the editor's terminal.
- If Claude Code is missing, Install Claude Code (Homebrew) runs
brew install --cask claude-codein a terminal. You need Homebrew for that (brew.sh). Afterwards you typeclaudeand sign in.
Nothing runs until you click.
Free and Premium
Setup, starting, limits, the statusline bridge and viewing agents and hooks are free. Creating or changing agents and hooks, the switch Keep the WebDonkey agent up to date and opening straight in Mission Control are Premium.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| No limits, only a note | The statusline bridge is missing, or Claude has not written a statusline yet | Install the bridge and type something in a Claude session |
| Almost done does not go away | The sign-in in the browser is not finished | Finish signing in in the terminal |
| The window only shows the note about WebDonkey | WebDonkey is not installed or too old | Install or update WebDonkey |
| Something looks outdated | The window still holds old values | ⋯ › Refresh |
See also
Usage, memory and plugins Free & Premium
Three sections of the Claude window show what Claude Code costs, what it reads at every start and what it is extended with. Usage turns your tokens into an approximate amount, Memory shows the files Claude always reads in the open project, and Plugins lists Claude Code's installed plugins. None of this starts Claude or costs tokens.
Where to find it
Open the Claude window (⌘3). Usage and Memory are expanded, Plugins opens with a click on its heading.
Usage
The first line, Today, gives the day's tokens, such as "1.2 M tokens", followed after "≈" by their approximate value in US dollars. This is free.
Premium adds the last 7 days:
- one bar per day. Hover over it to see date, tokens and amount for that day.
- the line 7 days with the total.
- the three models with the largest share, each with its approximate cost. If WebDonkey does not know a price for a model yet, it says Price follows.
Without Premium this spot says Usage history with Premium. If there was nothing in the period, it says No Claude usage in this period.
Where the numbers come from
The tokens come from the transcripts Claude Code keeps on your Mac. They are the same numbers as on WebDonkey's usage page (WebDonkey: Claude).
- Where Claude Code recorded the cost of a session itself, that amount counts.
- The rest is priced at Anthropic's list prices. WebDonkey reads the prices from Anthropic's pricing page at start and then once a day. If the page cannot be read, the prices built into WebDonkey apply.
- With a Claude subscription the amount is not your bill but the equivalent at API prices.
Memory
Memory shows what Claude reads at every start in the open project: the CLAUDE.md files and Claude's auto memory (MEMORY.md and the notes it lists).
- A thin bar shows the files as shares by size, each in its own colour.
- Below it are the number of files and their total size (Files: …).
- The list names the six largest with their size. Files that apply to every project carry the note For all projects. Entries from
MEMORY.mdshow the title they have there. - Show all lists every file, Show less goes back to the six largest.
- A click on a row or on a share in the bar opens the file in the editor.
If there is nothing, it says No memory files for this project yet. The section never writes anything, it only shows.
Large memory files cost context at every start. The bar shows quickly which file is worth trimming.
Plugins
The list shows every installed Claude Code plugin with name, origin (@ and the marketplace), version, level (User, Project, Local or Managed) and when it was last updated.
- Details shows what Claude Code reports about the plugin, including how many context tokens it costs.
- The on / off switch turns a plugin on or off. This is Premium. Without Premium it says Switching plugins on and off needs Premium.
- Changes apply to newly started sessions.
If no plugins are installed, it says No plugins installed.
Refresh
The window reads its values by itself. For the latest state right away, choose Refresh in the window menu (⋯). All sections are read again and expanded or collapsed as at the start.
Free and Premium
| What | Free | Premium |
|---|---|---|
| Usage today | yes | yes |
| Usage of the last 7 days, per day and model | no | yes |
| Memory files | yes | yes |
| Viewing plugins and details | yes | yes |
| Switching plugins on and off | no | yes |
Troubleshooting
- Today shows a dash: no usage could be read yet. Wait a moment or choose ⋯ › Refresh.
- A model shows Price follows: Anthropic has not published a price for the model yet, or WebDonkey has not read it yet. The tokens already count, the amount follows once the price is known.
- A memory file is missing: the section only shows files that exist and are not empty.
See also
The IDE bridge Free
A claude you start in one of the editor's terminals connects to the editor, just as it does with VS Code. Claude then sees your open file and selection, knows the marked problems and shows planned edits as a diff in the editor. There is nothing to set up.
Where to find it
The bridge is on out of the box. The switch is called Connect Claude Code and sits under Settings › Terminal. For this the editor registers with Claude Code in ~/.claude/ide.
What Claude gets from it
- The open file and your selection: Claude sees what you are pointing at.
- The problems the editor marks in the open files.
- A way to propose edits instead of writing them right away.
How to do it
- Start
claudein an editor terminal, for example with ⌘⎋. - Ask Claude for a change. When Claude proposes it, a tab Claude proposes: opens with the file name and the number of changes.
- The left side is the file as it is, the right side Claude's version. You can still edit the right side before accepting.
- Accept (or ⌘↩ in the diff) hands the right side back to Claude, and Claude writes the file.
- Reject, or closing the tab, tells Claude no.
Claude's own question in the terminal keeps working in parallel ("or answer in the terminal"). If you answer there, the tab closes. If a proposal is no longer open, it says This proposal is no longer open.
Connected?
The status bar shows a small dot in front of the ✳. Hover over it to read Claude connected, or with several, for example "2 Claude sessions connected".
Switching it off
- For all terminals: turn off Settings › Terminal › Connect Claude Code.
- For one conversation in Mission Control: the ⧉ switch at the message field takes the editor reference out (Send a selection to Claude).
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| Claude shows no diffs in the editor | claude runs in another program, not in an editor terminal |
Start claude in the editor terminal |
| No dot in the status bar | The bridge is switched off | Turn on Settings › Terminal › Connect Claude Code and restart claude |
| The tab suddenly disappears | You answered in the terminal | Nothing, the answer counts |
See also
Send a selection to Claude Free
You can point Claude at a file, a folder or a few lines without typing paths. The editor puts a reference like @File#L3-9 into Claude's prompt. Nothing is sent: you add your message and send it yourself.
How to do it
From the editor
- Select lines in a file, or just leave the cursor in the file.
- Press ⌥⌘K (command Send selection to Claude, also in the Edit menu).
- The reference is in Claude's prompt. Write your message and press Enter.
From the project tree
- Select one or more files or folders.
- Right-click, then Send to Claude.
You can also drag files onto a Claude terminal. In Mission Control the plus button Attach files or folders adds them. There they show as chips above the message field, and the X on a chip removes it again.
Which session?
- If exactly one Claude session runs, the reference goes there.
- If several run in this window, the editor asks Which Claude session?. Each session is a button of its own, a click picks it.
- If none runs, the editor asks under No Claude session running whether to start one. With Start Claude the reference waits and goes into the prompt as soon as Claude is ready.
A short message then tells you which prompt the reference is in and that it has not been sent yet. If Claude is waiting for an answer in the terminal, the editor inserts nothing. Answer there first, then send again.
Editor reference with every message
If Claude is connected through the IDE bridge, it also gets the file open in the editor and selected lines with every message.
- In Mission Control's message field a chip with ⧉ shows this reference. Its X (Stop sending) takes the file out for this session.
- The ⧉ switch to the left of the plus button turns the editor reference off and on for this conversation. While it is off, the conversation gets nothing from the editor.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| A message that nothing was inserted | Claude is waiting for an answer in its terminal | Answer in the terminal, then send again |
| A message that the prompt is not visible yet | Claude is still starting | Wait a moment and send again |
| ⌥⌘K does nothing | The focus is not in a file | Click into the file and press it again |