diff --git a/public/content/core-dependencies/pieces-os/long-term-memory.md b/public/content/core-dependencies/pieces-os/long-term-memory.md index 7ad64d5..82e4bab 100644 --- a/public/content/core-dependencies/pieces-os/long-term-memory.md +++ b/public/content/core-dependencies/pieces-os/long-term-memory.md @@ -66,34 +66,44 @@ The agentic foundation powers features like [Meeting Prep](/products/desktop/sin ### Pausing or Disabling LTM -When LTM is active, the Quick Menu shows a green `On` button. Click it to open a dropdown with timed pause options or a full disable: +When LTM is active, the Quick Menu shows a green `On` button. Click it to pause or turn capture off. You can pause *LTM-2.7* and *LTM Audio* for any length of time, from a few minutes to several days, instead of only fixed presets. + +Pieces shows a clear **Paused until** label so you always know when capture resumes. Use this for a confidential call, a stretch of personal browsing, or a few days off. | Option | Effect | | --- | --- | -| *Pause for 15 minutes* | Temporarily stops capture; resumes automatically | -| *Pause for 1 hour* | Temporarily stops capture; resumes automatically | -| *Pause for 6 hours* | Temporarily stops capture; resumes automatically | -| *Pause for 24 hours* | Temporarily stops capture; resumes automatically | +| *Custom pause* | Pause for a duration you choose (minutes, hours, or days); resumes automatically at the *Paused until* time | | *Turn Off* | Fully disables LTM until you re-enable it manually | - Use timed pauses when you want a temporary break—for example, during a private call or a personal browsing session—without losing your LTM context history. + Use a timed pause for a temporary break, such as a private call or personal browsing, instead of turning LTM off entirely. -You can also toggle LTM from within the Pieces Desktop App: +You can pause from: + +* The **PiecesOS Quick Menu** +* The **user popover** in Pieces Desktop (`User Profile` → hover `LTM-2.7`) +* **Settings** → `Long-Term Memory` in Pieces Desktop - Click your `User Profile` in the top left. + Click your `User Profile` in the top left of the Pieces Desktop App. - - Hover over `Settings` and select `Long-Term Memory`. + + Hover over `LTM-2.7` to choose a pause duration, or hover over `Settings` and select `Long-Term Memory` for full controls. For a full breakdown of every toggle and option in that settings panel, see [LTM Settings](/products/desktop/configuration/long-term-memory). +### When Capture Stops Automatically + +Capture slows down when you step away: + +* When your **screen is locked**, Pieces stops capturing entirely. +* When you go **idle**, Pieces captures less often instead of sampling at full rate, so an unattended laptop isn't recording a screen nobody is looking at. + *** ## LTM Audio diff --git a/public/content/core-dependencies/pieces-os/quick-menu.md b/public/content/core-dependencies/pieces-os/quick-menu.md index e2aeb1a..e534203 100644 --- a/public/content/core-dependencies/pieces-os/quick-menu.md +++ b/public/content/core-dependencies/pieces-os/quick-menu.md @@ -22,7 +22,7 @@ The **Quick Menu** is a lightweight popover for interacting with PiecesOS, locat | --------------------------------- | -------------------------------------------------------------------------- | | *Account* | Log in or log out of your Pieces account | | *Version* | Check for and install PiecesOS updates | -| *Long-Term Memory Engine* | Enable, pause, or disable LTM | +| *Long-Term Memory Engine* | Enable, pause (custom duration with **Paused until**), or disable LTM | | *Long-Term Memory Access Control* | Choose which apps LTM captures data from | | *MCP Servers* | View the SSE endpoint URL and MCP documentation links | | *Settings* | Launch on login, enabled apps, ML processing, telemetry, memory optimization | @@ -42,11 +42,11 @@ Below your account, the Quick Menu displays your current PiecesOS version. If an ## Long-Term Memory -Toggle the [LTM-2.7 Engine](/products/core-dependencies/pieces-os/long-term-memory) on or off, manage [Audio ingestion](/products/core-dependencies/pieces-os/long-term-memory#ltm-audio), and control which apps LTM captures data from via [Access Control](/products/core-dependencies/pieces-os/long-term-memory#long-term-memory-access-control). +Toggle the [LTM-2.7 Engine](/products/core-dependencies/pieces-os/long-term-memory) on or off, pause capture for a custom duration (with a **Paused until** label), manage [Audio ingestion](/products/core-dependencies/pieces-os/long-term-memory#ltm-audio), and control which apps LTM captures data from via [Access Control](/products/core-dependencies/pieces-os/long-term-memory#long-term-memory-access-control). Toggling LTM engine on or off in the Quick Menu -For the full breakdown—pausing, disabling, Audio setup, per-app toggles—see the [LTM-2.7 Engine](/products/core-dependencies/pieces-os/long-term-memory) page. +For all pause options, the **Paused until** label, Audio setup, and per-app toggles, see the [LTM-2.7 Engine](/products/core-dependencies/pieces-os/long-term-memory) page. ## MCP Servers diff --git a/public/content/desktop.md b/public/content/desktop.md index 84cf36d..5cfa5b7 100644 --- a/public/content/desktop.md +++ b/public/content/desktop.md @@ -80,7 +80,7 @@ Use [Conversational Search](/products/desktop/conversational-search) as your mai ## Configuration -Customize your Pieces Desktop App through *Settings*: **Account** (profile, Personal Cloud, backup, telemetry), **Long-Term Memory**, **MCP**, **Connectors**, **Appearance**, and **Troubleshooting**. Choose models from the Conversational Search chat picker; see [Models in chat](/products/desktop/conversational-search/models) for cloud vs local selection. +Customize your Pieces Desktop App through `Settings`: **Account** (profile, Personal Cloud, backup, telemetry), **Long-Term Memory**, **MCP**, **Connectors**, **Appearance**, and **Troubleshooting**. Choose models from the Conversational Search chat picker; see [Models in chat](/products/desktop/conversational-search/models) for model families and modes. Explore all configuration options to customize your Pieces Desktop experience. diff --git a/public/content/desktop/configuration/long-term-memory.md b/public/content/desktop/configuration/long-term-memory.md index f1bc1c8..c0afd58 100644 --- a/public/content/desktop/configuration/long-term-memory.md +++ b/public/content/desktop/configuration/long-term-memory.md @@ -44,6 +44,29 @@ Toggle the Long-Term Memory Engine on or off to control whether Pieces captures The Long-Term Memory Engine helps Pieces understand your workflow patterns and provide more contextual suggestions in Conversational Search. When disabled, Pieces won't capture or use workflow context. +### Pausing Capture + +Pause *LTM-2.7* and *LTM Audio* for a custom duration: minutes, hours, or days. Pieces shows a **Paused until** label so you know exactly when capture resumes. + +You can pause from: + +* This *Long-Term Memory* settings page +* Your `User Profile` popover (hover `LTM-2.7`) +* The [PiecesOS Quick Menu](/products/core-dependencies/pieces-os/quick-menu) + + + + Click your `User Profile`, hover over `LTM-2.7`, and choose a pause duration. Alternatively, open `Settings` → `Long-Term Memory` and pause from *Memory Formation*. + + + Check the **Paused until** indicator so you know when capture will pick back up automatically. + + + + + Capture also stops while your screen is locked, and slows when you go idle. For the full pause behavior, see [LTM-2.7 Engine](/products/core-dependencies/pieces-os/long-term-memory#pausing-or-disabling-ltm). + + ### App Access Control Manage which applications the Long-Term Memory Engine interacts with. This allows you to control what data sources Pieces uses when capturing workflow context. diff --git a/public/content/desktop/configuration/mcp.md b/public/content/desktop/configuration/mcp.md index cb01f1b..837fec9 100644 --- a/public/content/desktop/configuration/mcp.md +++ b/public/content/desktop/configuration/mcp.md @@ -95,14 +95,16 @@ For more use cases and detailed setup instructions, refer to the [MCP documentat ## MCP Connections -Connect Pieces to supported MCP clients with one click. Pieces writes to each client's global or user-level MCP config and, when supported, also creates the matching global rule or skill file automatically. +Connect Pieces to supported apps with one click. Pieces saves each app's connection settings for you and, when supported, also creates the matching rule or skill file automatically. + +Most apps connect with a simple local link. **Claude Desktop** is different: Pieces includes the connector it needs, so you can connect without installing anything extra. MCP Connections section showing supported clients with Connect buttons > MCP Connections section showing supported clients with one-click Connect buttons - Some MCP clients may need to be restarted or reopened before configuration changes appear. + Some apps may need to be restarted or reopened before the new settings appear. For Claude Desktop, Pieces shows a *Restart Claude Desktop* prompt with a `Restart Claude Desktop now` button when a restart is required. The MCP Connections section shows your connection status (e.g., "Connected 4 of 6") and a `Refresh Connections` button to update the status. @@ -111,7 +113,7 @@ The MCP Connections section shows your connection status (e.g., "Connected 4 of | Client | Description | | --- | --- | -| **Claude Desktop** | Connect Pieces to Claude Desktop for memory-backed conversations | +| **Claude Desktop** | Connect Pieces to Claude Desktop for access to all of your Personal Memories without any additional installation | | **Cursor** | Connect Pieces to Cursor so your IDE has access to long-term memory | | **GitHub Copilot** | Connect Pieces to GitHub Copilot for context-aware code suggestions | | **Codex** | Connect Pieces to Codex so both the CLI and IDE extension can connect to your memory via MCP | @@ -129,14 +131,21 @@ The MCP Connections section shows your connection status (e.g., "Connected 4 of Find the *MCP Connections* section below the Available Servers and View Documentation sections. + + When connecting **Claude Desktop** on Linux, quit Claude Desktop first if it is already running so Pieces can write the config safely. + Click the `Connect` button next to the client you want to configure. Pieces automatically writes the MCP configuration to that client's config file. - Restart or reopen the MCP client for the configuration changes to take effect. + Restart or reopen the MCP client for the configuration changes to take effect. For Claude Desktop, use `Restart Claude Desktop now` when the prompt appears. + + For the full Claude Desktop flow, including Snap and Flatpak notes, see [Pieces MCP + Claude Desktop](/products/mcp/claude-desktop). + + ### Managing Connected Clients Once connected, a green checkmark appears next to the client name. To disconnect or reconfigure: diff --git a/public/content/desktop/connectors/google-calendar.md b/public/content/desktop/connectors/google-calendar.md index 642665b..3c86930 100644 --- a/public/content/desktop/connectors/google-calendar.md +++ b/public/content/desktop/connectors/google-calendar.md @@ -68,7 +68,7 @@ Beyond direct calendar management, Pieces uses your calendar to enrich answers. Once connected, your calendar events flow into [Single-Click Summaries](/products/desktop/single-click-summaries) that use workflow context, including *Morning Brief*, *Standup Update*, and *Day Recap*. These summaries reflect what was actually on your schedule rather than what happened to be visible on your screen. -The *Google Calendar* connector is also the foundation for [Meeting Prep](/products/desktop/single-click-summaries/default-types#meeting-prep), a summary type that looks ahead at your upcoming meetings, cross-references each event with your Long-Term Memory, and generates a structured pre-read. +The *Google Calendar* connector is also the foundation for [Meeting Prep](/products/desktop/single-click-summaries/default-types#meeting-prep), a summary type that looks ahead at your upcoming meetings, cross-references each event with your Long-Term Memory, and generates a structured pre-read. In summary results, hover attendee names for [persona cards](/products/desktop/single-click-summaries#people-tags--anchors). Example prompts: diff --git a/public/content/desktop/conversational-search/setting-context.md b/public/content/desktop/conversational-search/setting-context.md index c979fc7..bf770d6 100644 --- a/public/content/desktop/conversational-search/setting-context.md +++ b/public/content/desktop/conversational-search/setting-context.md @@ -26,7 +26,7 @@ Control whether Conversational Search includes Long-Term Memory context in your Hover over `LTM-2.7` in the dropdown menu that appears. - To keep LTM active, ensure it is not paused or turned off. To disable, select a pause duration (15 minutes, 1 hour, 6 hours, 12 hours, or 24 hours) or choose `Turn Off`. When paused or off, Conversational Search will not include workflow history context. + To keep LTM active, ensure it is not paused or turned off. To pause temporarily, choose a custom duration (minutes, hours, or days), and Pieces shows a **Paused until** time. Alternatively, choose `Turn Off`. When paused or off, Conversational Search will not include workflow history context. Full details: [Pausing LTM](/products/core-dependencies/pieces-os/long-term-memory#pausing-or-disabling-ltm). diff --git a/public/content/desktop/single-click-summaries.md b/public/content/desktop/single-click-summaries.md index 0698fb0..4bfe186 100644 --- a/public/content/desktop/single-click-summaries.md +++ b/public/content/desktop/single-click-summaries.md @@ -26,12 +26,12 @@ Each summary type adapts dynamically to your workflow, meaning the same summary Click any summary card on the homepage and after a few minutes, you'll see your summary in the [Pieces Timeline](/products/desktop/timeline). - You can queue multiple unique summaries at once, but wait for the current one to finish before starting another of the same type. + You can run several Single-Click Summaries at once. Start a *Day Recap*, *Standup Update*, and *Meeting Prep* together and let them generate side by side. You no longer need to wait for one to finish before starting the next. ### Viewing Queued Summaries -When you generate a summary, it appears under the current day in Pieces Timeline with a "Queued" status. Expand the day section to track progress. +When you generate a summary, it appears under the current day in Pieces Timeline with a "Queued" or generating status. Expand the day section to track progress. The Timeline stays responsive while summaries generate, so you can keep scrolling and reading even with several in flight. @@ -55,12 +55,26 @@ Locate the summary you want to cancel under the current day in Pieces Timeline a ### Viewing Completed Summaries -When a summary finishes generating, it remains in the day section where it was queued. Click it to view detailed insights, related activities, and links to relevant documents or commits from your workflow. +When a summary finishes generating, it remains in the day section where it was queued. Click it to view detailed insights, related activities, and artifacts from your workflow. + +Summaries are based on **memories from a given time frame**—not a guess from whatever was on screen. Those memories can include vision, audio, clipboard activity, browser URLs you visited, files you opened, and people you collaborated with. A completed summary usually includes a high-level overview of that context plus people, URLs, files, next steps, and tasks. Files and sites cited in a summary are **clickable**, so you can open them directly. Completed summary with insights, related activities, and document links > Completed summary view showing full results with insights, related activities, and links to relevant documents +### People, Tags & Files + +Pieces detects people mentioned in your workstream and people you have collaborated with, then turns each name in a summary into a rich, hoverable reference. Hover any name to open a **persona card** showing who they are, how to reach them, their role, and how you two have worked together over time. + +*Tags* and *files/folders* in summaries work the same way: live references instead of plain text. + +This is especially useful when: + +* A summary mentions someone you've met once and can't quite place +* You're walking into a meeting and want context on an attendee without leaving the page +* You need to recall what you and a teammate last decided together + *** ## Explore Single-Click Summaries diff --git a/public/content/desktop/single-click-summaries/default-types.md b/public/content/desktop/single-click-summaries/default-types.md index 2517681..6fa729f 100644 --- a/public/content/desktop/single-click-summaries/default-types.md +++ b/public/content/desktop/single-click-summaries/default-types.md @@ -54,7 +54,7 @@ Helps you understand what's been occupying your attention and what matters most ## Standup Update *Three-part update: what you did, what's next, and blockers.* -Generates a ready-to-share standup format perfect for team meetings. Copy it directly into Slack, Teams, or your standup bot. +Generates a ready-to-share standup format perfect for team meetings. Copy it directly into Slack, Teams, or your standup bot. You can run Standup Update at the same time as other summaries, such as *Day Recap* or *Meeting Prep*. **When to use:** - **Daily standups** — Walk in prepared with your update written @@ -71,6 +71,8 @@ Generates a ready-to-share standup format perfect for team meetings. Copy it dir Analyzes your captured workflow context—recent documents, conversations, and activities related to each meeting's attendees and topics—and creates calendar events that give you time to review before you join. +Hover attendee names for [persona cards](/products/desktop/single-click-summaries#people-tags--anchors): who they are, how to reach them, and how you've worked together. + **When to use:** - **Block prep time** — Get calendar events for meeting preparation - **Review context** — See relevant docs and notes before important meetings @@ -84,7 +86,7 @@ Analyzes your captured workflow context—recent documents, conversations, and a ## Day Recap *Concise summary of your accomplishments, blockers, and feedback from today's activity.* -Compiles an end-of-day summary ready to share or save—so you have a clear record of what you got done. +Compiles an end-of-day summary ready to share or save, so you have a clear record of what you got done. Day Recap cites the files you had open and sites you visited, with clickable file references when available. **When to use:** - **Log off for the day** — Wrap up with a clear record of what you accomplished @@ -173,7 +175,7 @@ Surfaces your professional habits, strengths, and work patterns—giving you lan ## Collaboration Patterns *Identifies who you work with and how, revealing collaboration dynamics.* -Discovers your collaboration habits and team interaction patterns—showing your working relationships at a glance. +Discovers your collaboration habits and team interaction patterns, showing your working relationships at a glance. People named in the summary support the same [persona hover cards](/products/desktop/single-click-summaries#people-tags--anchors) as other summary types. **When to use:** - **Identify key collaborators** — See who you've been working with on a project diff --git a/public/content/desktop/timeline/ltm-rollups.md b/public/content/desktop/timeline/ltm-rollups.md index b2edfaa..5110d3e 100644 --- a/public/content/desktop/timeline/ltm-rollups.md +++ b/public/content/desktop/timeline/ltm-rollups.md @@ -20,7 +20,7 @@ Each roll-up contains structured information about your workflow period: * **Core Tasks & Projects** — What you worked on and problems solved * **Key Decisions & Discussions** — Important conversations and choices made -* **Documents & Code Reviewed** — Files and links you accessed (with deep links) +* **Documents & Code Reviewed** — Files and links you accessed (with deep links), based on files you had open and sites you visited during the window * **Follow-Up Actions** — What still needs attention Roll-ups created through Model Context Protocol (MCP) integrations display a "Formed with MCP" indicator. diff --git a/public/content/desktop/troubleshooting/linux.md b/public/content/desktop/troubleshooting/linux.md index 6996dba..d307c79 100644 --- a/public/content/desktop/troubleshooting/linux.md +++ b/public/content/desktop/troubleshooting/linux.md @@ -123,6 +123,12 @@ This section will display your Ubuntu version information. If you encounter persistent installation issues, consult online forums or community guides related to snap and Ubuntu-specific troubleshooting steps. +## Claude Desktop MCP on Linux + +Pieces supports Snap and Flatpak installs. For the Claude Desktop MCP connection from Desktop `Settings` → `MCP`, Claude only needs to point at the PiecesOS executable—no additional install is required. + +Quit Claude Desktop before `Connect` if it is running, then use `Restart Claude Desktop now` when prompted. Full steps: [Claude Desktop](/products/mcp/claude-desktop). + ## Restart & Retry If you've updated components, checked the hardware, and adjusted configurations without success, try restarting your machine and then try again. diff --git a/public/content/mcp.md b/public/content/mcp.md index 73fb47c..51462a6 100644 --- a/public/content/mcp.md +++ b/public/content/mcp.md @@ -147,16 +147,18 @@ Explore how quickly MCP enhances your productivity by delivering deep, personali To begin using Pieces MCP, [install and launch PiecesOS](/products/core-dependencies/pieces-os/manual-installation) on your system, then follow our integration documentation for setting up the MCP server within your favorite IDE or tool: -### One-Click Install (Cursor & VS Code) +### One-Click Install -If you use Cursor or VS Code, install Pieces MCP with a single click. Ensure [PiecesOS is running](/products/core-dependencies/pieces-os) and [Long-Term Memory is enabled](/products/core-dependencies/pieces-os/quick-menu#ltm-2-engine) first. +If you use Cursor, VS Code, or Claude Desktop, connect Pieces with one click from Pieces Desktop (`Settings` → `MCP` → `MCP Connections`). Ensure [PiecesOS is running](/products/core-dependencies/pieces-os) and [Long-Term Memory is enabled](/products/core-dependencies/pieces-os/quick-menu#ltm-2-engine) first. + +For **Claude Desktop**, Pieces includes everything needed to connect; no extra software to install. See [Claude Desktop](/products/mcp/claude-desktop) for the restart prompt and Linux Snap/Flatpak notes. ### Setup Tools -* [mcp-remote Stdio Bridge](/products/mcp/mcp-remote) — Connect stdio-only clients to PiecesOS -* [ngrok Setup](/products/mcp/ngrok-setup) — Expose PiecesOS for remote MCP access +* [Advanced Configuration](/products/mcp/mcp-remote): manual setup for apps that need a helper connection (Raycast, Zed, OpenClaw, and similar). Claude Desktop one-click does not need this. +* [ngrok Setup](/products/mcp/ngrok-setup): share PiecesOS for remote access ### Platform Integrations diff --git a/public/content/mcp/claude-cowork.md b/public/content/mcp/claude-cowork.md index 0f148cc..ebff8b7 100644 --- a/public/content/mcp/claude-cowork.md +++ b/public/content/mcp/claude-cowork.md @@ -46,9 +46,20 @@ Follow the instructions below for a detailed guide on setting up and configuring ## Connecting Pieces MCP to Claude Cowork -Cowork uses the **same MCP configuration as Claude Desktop**. You have two options: +Cowork uses the **same connection as Claude Desktop**. Prefer one-click setup in Pieces Desktop, where Pieces saves Claude Desktop's settings for you and you do not need to install anything else. -### Option 1: Via Connectors UI (Pro/Max/Team/Enterprise, for remote URLs) +### Option 1: One-Click via Pieces Desktop (Recommended for local use) + + + + In Pieces Desktop, open `Settings` → `MCP`, then click `Connect` next to **Claude Desktop**. Follow the [Claude Desktop guide](/products/mcp/claude-desktop) if you need the full walkthrough (including Linux quit-first and restart prompts). + + + Use `Restart Claude Desktop now` when prompted so Cowork picks up the shared connection. + + + +### Option 2: Via Connectors UI (Pro/Max/Team/Enterprise, for remote URLs) For remote access, you need a public HTTPS URL. Set up [ngrok](/products/mcp/ngrok-setup) or another tunnel first. @@ -73,13 +84,11 @@ For remote access, you need a public HTTPS URL. Set up [ngrok](/products/mcp/ngr -### Option 2: Via JSON Config with stdio Bridge (recommended for local use) +### Option 3: Advanced (manual config file) - - **Recommended when PiecesOS and Claude Desktop are on the same machine.** Uses the localhost URL via an mcp-remote bridge. - +Use this only if you cannot use one-click `Connect` and need to edit Claude's settings file by hand. See [Advanced Configuration](/products/mcp/mcp-remote) for details. -Install `mcp-remote` globally with a pinned version for security: +Install the helper package with a pinned version: ```bash npm install -g mcp-remote@0.1.38 @@ -100,7 +109,7 @@ Edit `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) o } ``` -See the [Claude Desktop guide](/products/mcp/claude-desktop) and [MCP Bridge](/products/mcp/mcp-remote) for full details. +See the [Claude Desktop guide](/products/mcp/claude-desktop) and [Advanced Configuration](/products/mcp/mcp-remote) for full details. ## Using Pieces Tools in Claude Cowork diff --git a/public/content/mcp/claude-desktop.md b/public/content/mcp/claude-desktop.md index 0ff4070..338425c 100644 --- a/public/content/mcp/claude-desktop.md +++ b/public/content/mcp/claude-desktop.md @@ -51,11 +51,13 @@ Follow the instructions below for a detailed guide on setting up and configuring ## Setting up Pieces MCP for Claude Desktop -There are **three methods** to set up the Pieces MCP for Claude Desktop: use the one-click setup in Pieces Desktop, configure manually, or use the Pieces CLI. +Connecting Claude Desktop used to mean installing extra tools on your machine. Pieces now includes everything you need on macOS, Windows, and Linux. Pick Claude Desktop, click `Connect`, and Pieces writes the setup for you. + +The recommended path is one-click setup in Pieces Desktop. Advanced options (Pieces CLI or editing a config file by hand) are below if you need them. ### One-Click Setup via Pieces Desktop (Recommended) -The fastest way to connect Pieces MCP to Claude Desktop is through the MCP Connections feature in Pieces Desktop. +Connect Claude Desktop from *MCP Connections* in Pieces Desktop. Pieces configures Claude for you using a connection helper that ships inside PiecesOS; nothing else to install. @@ -66,29 +68,33 @@ The fastest way to connect Pieces MCP to Claude Desktop is through the MCP Conne Scroll down to the *MCP Connections* section. You'll see a list of supported clients with `Connect` buttons. - - Click the `Connect` button next to **Claude Desktop**. Pieces automatically writes the MCP configuration to Claude Desktop's config file. + + On Linux, especially Snap or Flatpak installs, quit Claude Desktop before connecting. If Claude is still running, it can overwrite the settings Pieces just saved. Pieces notices when Claude Desktop is already open and walks you through quitting first. - - If Pieces detects missing dependencies (like Node.js/npx), a dialog appears with installation instructions. Install the missing dependencies using the provided commands, then click `Retry`. + + Click the `Connect` button next to **Claude Desktop**. Pieces saves the connection settings for you. You do not need to install anything else. - Fully quit and reopen Claude Desktop for the configuration changes to take effect. Once connected, a green checkmark appears next to Claude Desktop in the MCP Connections list. + When the new settings need a restart, Pieces shows a *Restart Claude Desktop* prompt. Click `Restart Claude Desktop now` to relaunch Claude, or `Got it` if you will restart yourself. Once connected, a green checkmark appears next to Claude Desktop in the MCP Connections list. + + Snap and Flatpak installs are supported. As long as Claude Desktop points at the PiecesOS executable, the MCP connection works with no additional install. + + To disconnect later, click the `⋮` menu next to the connected client and select **Disconnect**, or click the red `✕` next to the connection entry. -### Method 1: Manual Configuration (Direct MCP Command) +### Advanced: Manual Configuration (Direct MCP Command) -This method involves editing Claude Desktop’s MCP configuration file to point directly to a CLI command that starts the Pieces MCP server. +This method edits Claude Desktop’s MCP configuration file to point at a CLI command that starts the Pieces MCP server. Use one-click setup above unless you need a custom path. - With this method, the Claude MCP config points to the Pieces CLI executable and runs `pieces mcp start` whenever Claude starts. This is different from using the CLI to configure Claude directly (Method 2). + With this method, the Claude MCP config points to the Pieces CLI executable and runs `pieces mcp start` whenever Claude starts. This is different from using the CLI to configure Claude directly (the next advanced method). Claude Desktop manual MCP configuration process @@ -172,7 +178,7 @@ This method involves editing Claude Desktop’s MCP configuration file to point -### Method 2: Using the Pieces CLI +### Advanced: Using the Pieces CLI This method uses the Pieces CLI to automatically set up and configure Pieces MCP for Claude Desktop. @@ -263,15 +269,21 @@ If you're experiencing issues integrating [Pieces MCP](/products/mcp) with Claud 2. **Confirm LTM Engine Activation**\ [Long-Term Memory (LTM-2.7)](/products/core-dependencies/pieces-os/quick-menu#ltm-2-engine) must be enabled in PiecesOS. -3. **Single MCP Instance**\ +3. **Restart Claude Desktop**\ + After one-click Connect, use `Restart Claude Desktop now` in the Pieces prompt (or fully quit and reopen Claude) so the new config loads. + +4. **Linux: Quit Claude Before Connecting**\ + If Connect fails or the connection disappears on Linux, quit Claude Desktop completely, connect again from *MCP Connections*, then restart Claude. See [Linux troubleshooting](/products/meet-pieces/troubleshooting/linux) for Snap and Flatpak notes. + +5. **Single MCP Instance**\ Avoid running multiple Pieces MCP instances in different apps simultaneously. -4. **Check MCP Server Status in Claude**\ +6. **Check MCP Server Status in Claude**\ Use the Developer Console (`Ctrl+Shift+I`) to confirm connection messages. -5. **Review Configuration**\ - If using *Method 1*, ensure your JSON paths are correct.\ - If using *Method 2*, rerun: +7. **Review Advanced Configuration**\ + If you used a manual JSON edit, ensure paths are correct.\ + If you used the Pieces CLI, rerun: ```powershell pieces mcp setup diff --git a/public/content/mcp/mcp-remote.md b/public/content/mcp/mcp-remote.md index 905bb3f..4112afe 100644 --- a/public/content/mcp/mcp-remote.md +++ b/public/content/mcp/mcp-remote.md @@ -3,17 +3,21 @@ title: MCP Bridge path: /mcp/mcp-remote visibility: PUBLIC status: PUBLISHED -description: Use the mcp-remote bridge to connect stdio-only MCP clients to PiecesOS, enabling Long-Term Memory in Raycast, Zed, Claude Cowork, and more. -metaTitle: Set Up the MCP Remote Bridge | Pieces Docs -metaDescription: Use mcp-remote to connect stdio-only MCP clients to PiecesOS. Step-by-step guide for Raycast, Zed, Claude Cowork, OpenClaw, and remote setups. +description: Connect apps that need a helper setup to PiecesOS so they can use Long-Term Memory, such as Raycast, Zed, and OpenClaw. +metaTitle: Advanced MCP Configuration | Pieces Docs +metaDescription: Manual setup for apps that need a helper connection to PiecesOS. Step-by-step for Raycast, Zed, OpenClaw, and remote setups. --- ## MCP Bridge -Many MCP clients—including Raycast, Zed, and Claude Cowork—only support **stdio** (standard input/output) connections. PiecesOS exposes its MCP server over **HTTP** and **SSE**. The [mcp-remote](https://github.com/geelen/mcp-remote) bridge translates between these protocols so stdio-only clients can connect to PiecesOS and use [Pieces Long-Term Memory](/products/core-dependencies/pieces-os#ltm-27). +Some apps, including Raycast, Zed, and OpenClaw, need a small helper to talk to Pieces. This page covers that advanced, manual setup. Use it when your app is not available in one-click Connect. - The easiest way to bridge MCP is with the Pieces CLI—run `pieces mcp setup` and select your platform. Use manual setup below only for clients not supported by the CLI or when you need custom config (e.g., remote URLs). + **Claude Desktop** does not need this page for the usual setup. Use one-click `Connect` in Pieces Desktop (`Settings` → `MCP`), where Pieces includes the connection helper and saves the settings for you. See [Claude Desktop](/products/mcp/claude-desktop). + + + + For other apps, the easiest path is often the Pieces CLI: run `pieces mcp setup` and select your platform. Use the manual steps below only when your app is not listed or you need a custom address (for example, a remote URL). ## Easiest Option: Pieces CLI @@ -125,7 +129,7 @@ PiecesOS exposes two endpoints. For `mcp-remote`, use the **SSE** endpoint—it - Edit `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows): + Prefer one-click `Connect` for [Claude Desktop](/products/mcp/claude-desktop), since Cowork shares that setup. Use the steps below only for advanced manual configuration. ```json { @@ -140,7 +144,7 @@ PiecesOS exposes two endpoints. For `mcp-remote`, use the **SSE** endpoint—it } ``` - See [Claude Cowork integration](/products/mcp/claude-cowork) for full setup. + Edit `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows). See [Claude Cowork](/products/mcp/claude-cowork) for full setup. diff --git a/public/content/meet-pieces/troubleshooting/linux.md b/public/content/meet-pieces/troubleshooting/linux.md index 0d0659f..b5bdf13 100644 --- a/public/content/meet-pieces/troubleshooting/linux.md +++ b/public/content/meet-pieces/troubleshooting/linux.md @@ -121,6 +121,14 @@ This section will will display your Ubuntu version information. If you encounter persistent installation issues, consult online forums or community guides related to snap and Ubuntu-specific troubleshooting steps. +## Claude Desktop MCP on Linux + +Pieces supports Snap and Flatpak installs. For the [Claude Desktop](/products/mcp/claude-desktop) MCP connection via `Settings` → `MCP` → `MCP Connections`, Claude only needs to point at the PiecesOS executable—no additional install is required. + +* Quit Claude Desktop completely before clicking `Connect` if Claude is already running. Otherwise Claude can overwrite the settings Pieces just saved. +* When prompted, use `Restart Claude Desktop now` so the new settings load. +* If Connect fails after a Snap or Flatpak update, refresh PiecesOS, quit Claude, connect again, then restart Claude. + ## Restart & Retry If you’ve updated components, checked hardware, and adjusted configurations without success, restart your machine and try again.