Ctrl+V does nothing in Power view: how to paste (and the build that fixed it)

You press Ctrl+V in the Power view terminal and nothing happens. No error, no beep, no text at the prompt, exactly as if the key were dead. One performer wrote in and put it plainly: in the new version of Booked Solid, it is not allowing the "paste" command in the power view - I think it is vital. Both halves of that are right. Ctrl+V does nothing was a real defect on our side, not you doing anything wrong, and it is fixed from version 1.7.11 onward. This article gives you the key combinations that work today, how to confirm you are on a build with the fix, and then the rest of what Power view does once paste is out of your way.

Copy and paste in Power view: the keys that work

The why is worth thirty seconds, because it explains behaviour that otherwise looks like a broken app. The pane at the top of Power view is a real terminal, and a terminal does not arrive with a clipboard of its own. Every copy and paste shortcut in there has to be wired on by hand, key by key. We wired Ctrl+Shift+V and Cmd+V, and missed the most obvious key of all. On builds before 1.7.11, plain Ctrl+V reached the terminal as an ordinary keystroke and quietly went nowhere. That silence is the whole reason it looked like paste had been left out on purpose.

These are the combinations:

• Windows or Linux - Ctrl+Shift+V. Hold Shift as well as Ctrl. This worked before the fix and still works after it.
• Windows or Linux, on 1.7.11 and newer - plain Ctrl+V as well.
• Mac - Cmd+V. On a Mac, plain Ctrl+V is deliberately left alone so the shell can still use it, so Cmd+V is the key to reach for on any build.

If you can't paste in the terminal on an older build, Ctrl+Shift+V is the one to try first. It is a single Shift key away from what you were already pressing, and it needs no update at all.

Copying works the other way round: select the text in the terminal with your mouse first, then press Ctrl+C or Cmd+C. The copy only fires when something is actually selected. With nothing selected, Ctrl+C keeps its old terminal meaning and interrupts whatever is running. That is deliberate. You would not want the stop key to stop working because we had borrowed it for the clipboard.

Three things that will not bring paste back

People burn real time on these, so here they are up front.

• Right-clicking the terminal. Almost everyone tries this first, and it is a dead end. The terminal pane has no right-click menu, so there is no Paste item hiding in one. Skip it.
• Hunting for a setting. There is no paste switch anywhere in Settings. Nothing in there turns this on or off, so there is nothing to find.
• Reinstalling the same build. A reinstall that lands you back on the same version number changes nothing about paste. Only a newer version, or the key combinations above, will do it.

Getting the fix: version 1.7.11 and newer

Plain Ctrl+V pastes from 1.7.11 onward, and every build since has kept it. Ctrl+Shift+V and Cmd+V keep working after the fix as well, so nothing you have already learned stops working.

The fix arrives on its own through the app's auto-update, and Booked Solid checks for a new version every time it launches. To nudge it along:

1. Quit Booked Solid completely, then reopen it. On a Mac use Cmd+Q: closing the window with the red button leaves the app running, and the check only happens on a real launch.
2. Open Settings, stay on General, and scroll to the bottom to the Updates block. The line there reads "You're running Booked Solid" followed by your version number.
3. If that number is 1.7.11 or higher, go back to Power view and retest Ctrl+V. If it is lower, the update has not landed yet, and Ctrl+Shift+V or Cmd+V is your paste key in the meantime.

Read the number before you retest, every time. Retesting a fix on a build that never changed is the single biggest time waster in this whole area, and the update window is not proof on its own.

There is one catch that hits exactly the people this article is written for. If your version number starts with 1.7 and quitting and reopening does not move it, your copy is an older build whose updater still checks the previous owner's update server. It will report that you are up to date forever, and the 1.7.11 fix will never reach you that way. The way out is one manual download from https://booked.kivimedia.co/download, installed straight over your current copy. Your leads, history, settings and license all stay where they are. Which version am I running walks through that download in full, and How updates work: the update badge and Restart & install explains the badge and the Restart & install button if an update is sitting there waiting for you.

The composer box: the way in that never had this problem

When Power view is running the raw agent, a composer box sits below the terminal. It is worth understanding what it is, because the difference is the source of most of the confusion here: the composer is an ordinary text box, and the terminal pane above it is not. Your normal paste key works in the composer on every platform and always did, along with undo and text selection, which raw terminals usually make painful.

1. Type or paste your command or request into the composer textarea.
2. Press Enter or click Send to pass it straight to the terminal. Shift+Enter gives you a new line without sending.

Multi-line text is handled properly here too. Paste a block of several lines and press Enter, and the whole block is handed over first and submitted a beat afterwards, rather than each line firing off as its own command as you paste.

When Power view is running the default Booked Solid CLI instead of the raw agent, the composer is not on screen. In that case the key combinations at the top of this article are how text gets in.

Switch to Power view

Power view is an embedded terminal inside every task tab, for performers who are comfortable with a command line and want to work closer to the metal. Most people never need it, since Chat does everything in plain words, but if you know your way around a terminal the full workspace session is one click away.

1. Open any task tab.
2. In the switcher above the conversation, click Power view (Chat is selected by default).
3. To return, use the toggle link: it reads Power-user view from the simple side and Back to simple view from the terminal side.

What you'll see

Power view shows a real embedded terminal running inside your workspace. When it boots, a Booked Solid banner animation confirms the session is up. By default, the simple view runs the Booked Solid CLI, the same branded engine the rest of the app uses, so everything you do stays inside your Booking HQ.

Running the raw agent

Beyond the default Booked Solid CLI, Power view can run the raw agent directly. Before that session starts, the app verifies your Claude sign-in first, so you are never dropped into a session that cannot respond.

If you have picked a different assistant runtime, two confirmations protect you:

• Use your saved key for this run? - some runtimes run on a paid API key you have saved. This modal asks before any of that key is spent: choose Yes, use my key to proceed or Cancel to back out. Nothing is charged without this confirmation.
• Connect modal - if the runtime you picked is not connected yet, a modal explains what to set up first. Click Got it to dismiss it, complete the connection, and try again.

If the terminal fails to start

When the terminal session cannot start, a terminal-failure notice line appears in the view instead of leaving you staring at a blank screen. Switch back to simple view and try again, or restart the app if it persists. Chat keeps working normally either way, so a terminal hiccup never blocks your booking work.

When to use which view

• Chat (simple view) - plain-words requests, drafts, and answers. The right choice for day-to-day booking work.
• Power view - direct terminal access for advanced users who want to drive the workspace session by hand.

If paste still does nothing

Submit a ticket from this help center and tell us three things: the version number from Settings > General, whether you are on Windows, Mac or Linux, and which key combinations you have tried. Those three answers are usually enough for us to tell you in one reply whether you are looking at an update that has not landed or something new, and we would rather hear about it than have you working around it quietly. This one reached us because a performer took the time to write in about a single key, and it was fixed the same day.