Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions pine/en/advanced/server.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,39 @@ PINE_PASSWORD=... node apps/desktop/.vite/server/server.mjs --pair
A removed device can never connect again. `--data-dir` / `PINE_DATA_DIR` must match what the server runs with.
- A device can't pair other devices: pairing can only be started from the terminal.

## WeChat remote

A server can also take [WeChat remote](../configuration/wechat.md), so an always-on machine receives tasks from WeChat at any time. Connecting needs an interactive terminal, because it shows a QR code and asks for the code WeChat sends:

```sh
PINE_PASSWORD=... node apps/desktop/.vite/server/server.mjs --wechat-bind
```

The terminal shows a QR code; scan it with WeChat on your phone and confirm, then send any message to the bot in WeChat and type the 6-digit pairing code it replies with into the terminal. When Pine runs as a service, stop the service and run it once in the foreground to connect (with Docker, use `docker run -it`); after that, start it as usual. The connection is kept in the data directory.

Check the status, disconnect and change settings with the `wechat` subcommand; `--data-dir` / `PINE_DATA_DIR` must match what the server runs with:

```sh
node apps/desktop/.vite/server/server.mjs wechat status
node apps/desktop/.vite/server/server.mjs wechat unbind
node apps/desktop/.vite/server/server.mjs wechat config --ceiling auto-approve --default-project none
```

| `wechat config` option | What it does |
| --- | --- |
| `--ceiling <mode>` | Highest approval mode: `let-me-review`, `auto-approve`, `autonomous` or `yolo` |
| `--default-mode <mode>` | Approval mode of sessions started from WeChat, never above the ceiling |
| `--default-project <id or none>` | Project `.new` starts sessions in; `none` is the temporary workspace |
| `--allow-high-risk <yes or no>` | Whether high-risk actions can be approved from WeChat |
| `--allow-files <yes or no>` | Whether files can be sent to WeChat |
| `--language <zh, en or auto>` | Language of the replies in WeChat |
| `--pause` / `--resume` | Stop / resume acting on WeChat messages |

A running server applies a change when it receives `SIGHUP` (`kill -HUP <pid>`) or restarts. When the login expires and WeChat needs a new scan, the log says so; run `--wechat-bind` in a terminal again as above.

> [!WARNING]
> Setting the ceiling or default mode to `yolo` prints a warning: anyone who gets into that WeChat account controls this server.

## Differences from the desktop app

- The data directory is separate from the desktop app's, and projects and sessions aren't shared by default. You can point `--data-dir` at any directory, but don't let the desktop app and the server use the same one at the same time.
Expand Down
58 changes: 58 additions & 0 deletions pine/en/configuration/approvals.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
---
title: "Approvals and automatic review"
description: "The four approval modes, the automatic approval path, what an approval card shows, and which actions always ask you."
order: 2
---

# Approvals and automatic review

## Approval modes

Each session has an approval mode at the bottom of the composer that decides whether the agent asks you before risky actions. The mode is saved with the conversation and shared between the desktop app and remote devices.

| Mode | Who decides |
| --- | --- |
| **Let Me Review** | Every risky action shows an approval card for you to decide |
| **Auto Approve** | The approval model reviews first; you get a card only when it is unsure or thinks you should confirm |
| **Autonomous Work** | The approval model reviews and tries not to stop for you, except for the actions listed below |
| **YOLO** | No permission constraints; asks you to confirm before enabling |

A session or sub-session the agent starts runs in the same approval mode as the session that started it, or a stricter one, never a looser one.

## Automatic approval path

In **Auto Approve** and **Autonomous Work**, choose who reviews in **Pine Settings › Agent › Automatic approval path**:

- **Model review**: every review goes to the approval model set in **Models**.
- **Decision model** (Beta): the **Decisions screening model** screens first. Calls it allows proceed directly, and calls that need you open a card; denied calls, or calls the screening could not handle, go to the approval model for the final decision and rationale. Needs OpenRouter; model review is used until it is configured.

Every automatic review is recorded. Open a tool call in the conversation, and **Review history** lists each screening or model review with the model actually used, its outcome and its reason. Outcomes are shown in bold with their own icon and color: green "Allowed", amber "Denied", blue "User confirmation required", grey "Sent for model review" and red "Review failed". The records remain when you reopen the conversation.

## Approval cards

When you need to decide, an **Approval required** card takes the composer's place:

- **Approve**, **Reject**, or **Reject with guidance**: type what you want instead; Enter sends, `Shift + Enter` adds a line, and `Esc` returns to the buttons.
- When automatic review hands a call to you, the card starts with one sentence on what the operation does and a short **Risks** list, worded for your **User profile › Technical background**. The **Explained by the approval model** label reminds you that what actually runs is the original parameters.
- **Technical details** (collapsed) holds why Pine asked, the agent's description, the original parameters and the reviewer's notes.
- On the Decision model path, Pine waits up to about 10 seconds for the plain-language account before showing the card; if it is not ready in time, the card appears with Technical details open and the account fills in when it arrives.
- When enabling a new tool would make the provider reprocess a very long context at full price, the card offers **Activate now**, compressing first and then continuing, or stopping the run.

With **Notify for approvals and questions** on, approvals raise a system notification while Pine is in the background, and you can approve or deny right from it.

## Actions that always ask you

These actions show a card in every approval mode, YOLO included:

- **Adding or changing an MCP server**: adding, changing, renaming or turning on an MCP server. The card names the server, the command it runs on this computer with your permissions outside Pine's sandbox (or the address it connects to), where it applies (**All projects** or this project only), and the names of the credentials it receives (values hidden).
- **Deleting a session**: a session open in a tab stops and its tab closes. Deleting a session also deletes its sub-sessions, and the confirmation says how many.
- **Changing a project**: creating, renaming, adding or removing folders, changing the working folder, setting the icon and accent color, or deleting it. The card's details list what will change.

In **Let Me Review**, organizing session folders, starting new sessions, and reading unrelated sessions also ask first.

## Computer Use

The first time the agent controls a desktop app or browser tab, it asks for control **for the current task**: one card in Let Me Review, and an automatic review in Auto Approve and Autonomous Work. Once granted, ordinary clicks, typing, scrolling, app switching and navigation continue without per-action reviews. The grant ends when the run finishes, you click **Stop response**, or the approval mode changes, and it is not restored when you reopen the session. OS permission requests and browser extension installation are approved separately.

> [!WARNING]
> While the grant is active, consequential actions such as payments, sending, publishing, irreversible deletion, security changes or sharing sensitive information with a new recipient rely on the agent choosing to ask you first, not on a separate check of each click. For that kind of work, stay in **Let Me Review**.
40 changes: 40 additions & 0 deletions pine/en/configuration/automations.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
---
title: "Automations, Skills and MCP"
description: "Unattended automations, reusable Skills, and MCP servers that connect outside tools."
order: 5
---

# Automations, Skills and MCP

All three managers are in the **More** menu at the top of the left sidebar, and each has a shortcut. Each one offers **Manage with Pine**: it starts a new session with the matching authoring tools already on, so you describe what you want and Pine writes it.

## Automations

**Automations** (`Mod + U`) are work Pine does on its own when a time, a file change or a website update calls for it. The easiest way to create one is to tell Pine in a conversation what you want done automatically; it shows an automation approval card listing the triggers, what it will read, write and reach, and any warnings, for you to approve.

Triggers: **Schedule**, **Folder change**, **System event**, **Website or feed check** and **Manual**, or several at once.

The manager has three tabs:

- **Activity**: each run with its status, such as **Running**, **Found something**, **Nothing new** or **Failed**. **Mark all as read**, or turn on **Show runs with nothing new**. Opening a run opens its session.
- **Automations**: each automation's triggers and permissions, with its state **On**, **Off** or **Paused**; **Run now**, **Edit definition** as JSON and **Check** it, or delete it.
- **Secrets**: values automations can use, such as API tokens. They are encrypted on this computer, given only to the automations that reference them, and hidden from what the agent reads; they can be changed only in the Pine desktop app on this computer.

Each run is a session in the project, marked with a workflow icon.

> [!NOTE]
> Automations run only while Pine is running. To keep them going after you close the window, turn on **Keep running in the background** in **General**.

## Skills

**Skills** (`Mod + S`) are reusable ways of working: instructions that tell the agent how to do a kind of task and which tools it may use.

- **Global** Skills are available to every project but are switched on per project; **Project** Skills belong to the current project only.
- Create, edit, enable per project, or delete them.

## MCP servers

**MCP servers** (`Mod + /`) connect outside tools to the agent through MCP. Each server is available to **All projects** or to the current **Project** only; add, edit, enable, remove and refresh their status.

> [!WARNING]
> A local MCP server runs with your user permissions, outside Pine's sandbox. That is why adding, changing, renaming or turning on an MCP server asks you in every approval mode, with a card that shows the command it runs or the address it connects to. Add only servers you trust.
39 changes: 39 additions & 0 deletions pine/en/configuration/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
---
title: "Advanced configuration"
description: "Every optional feature and setting in Pine: what each one does, its default, and where to find it."
order: 35
---

# Advanced configuration

[Using Pine](../using-pine.md) covers the basics of projects, sessions and approvals. These pages go through Pine's optional features and settings one by one: what each does, what it defaults to, and where to turn it on. None of them are required; look up a topic when you need it.

> [!NOTE]
> `Mod` means `Cmd` on macOS and `Ctrl` on Windows. Interface text follows Pine's English interface.

## Find by topic

- [Settings reference](settings.md): every option in the General, Appearance, Models, Agent, User profile and Projects sections of **Pine Settings**
- [Approvals and automatic review](approvals.md): the four approval modes, the automatic approval path, what an approval card shows, and which actions always ask you
- [Working with sessions](sessions.md): steering, quotes and follow-ups, attachments, interim answers, interactive answers, context and cost, sub-sessions, and letting the agent organize sessions and projects
- [Workbench and file previews](workbench.md): the workbench panels, file details, preview comments, the audio and video player, and enlarging images
- [Automations, Skills and MCP](automations.md): unattended automations, reusable Skills, and MCP servers that connect outside tools
- [Remote control](remote.md): Browser access, pairing a phone or other device through Aldine, keeping the computer awake, running in the background and the tray menu
- [WeChat remote](wechat.md): sending Pine tasks from your own WeChat, and every command available there
- [Keyboard shortcuts](shortcuts.md): every keyboard shortcut

## Where the settings are

Click the gear in the title bar to open **Pine Settings**. The sections are listed on the left (on a phone, the list comes first):

| Section | Main contents | See |
| --- | --- | --- |
| **General** | Language, currency, Monet mode, completion signal, notifications, quick composer, running in the background, diagnostic logging | [Settings reference](settings.md) |
| **Appearance** | Color mode, default color theme, Working glow, sidebar material, inverted documents | [Settings reference](settings.md) |
| **Models** | Model catalog refresh, title generation, approval, image and video generation, Decisions screening model | [Settings reference](settings.md) |
| **Agent** | Interactive answers, Interim answers, automatic approval path, context compaction, web tools, approximate location | [Settings reference](settings.md) |
| **User profile** | Nickname, pronouns, communication style, technical background, personal details, custom instructions | [Settings reference](settings.md) |
| **Projects** | Every project and its data usage; clearing temporary files and attachments | [Settings reference](settings.md) |
| **Remote control** | Keeping awake, pairing devices through Aldine, Browser access, WeChat | [Remote control](remote.md), [WeChat remote](wechat.md) |

Automations, Skills and MCP servers are not in the settings dialog but in the **More** menu at the top of the left sidebar; see [Automations, Skills and MCP](automations.md).
63 changes: 63 additions & 0 deletions pine/en/configuration/remote.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
---
title: "Remote control"
description: "Browser access, pairing a phone or other device through Aldine, keeping the computer awake, running in the background and the tray menu."
order: 6
---

# Remote control

**Pine Settings › Remote control** (desktop app only) lets you use the Pine on this computer from other devices. Every remote option works only while Pine is running and the computer is awake. To send tasks from WeChat, see [WeChat remote](wechat.md).

## Browser access

**Browser access** serves Pine's full interface to a browser, and is required for remote control through Aldine. Before turning it on, set an **Access password** (at least 8 characters) that browsers sign in with.

| Option | What it does |
| --- | --- |
| **Require password** | On by default. Turn it off only when something in front of Pine, such as Cloudflare Access, already signs people in; once off, anyone who reaches the address controls Pine and can run commands on this computer without signing in |
| **Stay signed in** | How long a browser stays signed in after entering the password: **Until the browser closes**, 1 day, 7 days or 30 days |
| **Allow LAN access** | Other devices on your network can open Pine. Traffic is unencrypted HTTP, so only use networks you trust |
| **Public address** | When a reverse proxy or a tunnel such as Cloudflare Tunnel serves Pine, its address, such as `https://pine.example.com` |
| **Port** | The port Pine listens on; open the access link again after changing it |
| **Access link** | Opens Pine at `127.0.0.1` on this computer; copy it or open it in a browser |
| **Signed-in browsers** | **Sign out all** makes every browser enter the password again. Changing the password also signs them out |

> [!CAUTION]
> Anyone who can sign in through Browser access can read your projects, run agents and run commands on this computer. Don't reuse the access password anywhere else.

## Remote control via Aldine

**Remote control via Aldine** pairs any device by QR code or link, with no port forwarding and end-to-end encryption.

1. Turn on **Browser access** first.
2. Click **Pair a device**, then scan the QR code with the other device's system camera, or open the pairing link in its browser. The dialog shows how long the code and link stay valid; after that, click **New code**.
3. Confirm the pairing on this computer. The dialog shows this computer's fingerprint so you can check it.

> [!TIP]
> Use the system camera and the native browser, not the scanners built into chat or payment apps.

**Paired devices** lists each device with when it was paired and last connected; **Rename** or **Remove** it. A removed device disconnects at once and must pair again.

On a phone:

- After adding the Pine Remote web page to your Home Screen, add computers inside that app with **Scan pairing code** or **Paste pairing link**, so they are saved there. Extra text around a pasted link is ignored.
- With several computers paired, **Switch computer** returns to the list of computers, where you can also add another.
- On a phone, Pine uses a layout for small screens: dialogs fill the screen, and lists and details are shown one at a time.

## Keeping the computer awake

**Keep the computer awake while remote control is on**, at the top of the section, is off by default. When on, the computer does not go to sleep while Browser access is on or WeChat is receiving tasks; the display can still turn off, and closing the lid still sleeps. When no remote control is on, the computer sleeps as usual.

## Running in the background and the tray menu

With **Keep running in the background** on in **General**, closing the last window keeps Pine in the menu bar (macOS) or notification area (Windows). The tray menu has:

- **Open Pine** and **Quick composer**
- Switches for **Browser access**, **Remote Control via Aldine** and **WeChat remote**
- **Keep computer awake for remote control**
- **Manage more settings…**, which opens the Remote control settings
- The number of running sessions, and **Quit Pine**

To stop automations and every kind of remote control, quit Pine from the tray menu. Pine asks before quitting while sessions are running, remote control is on, or WeChat remote is listening.

To keep remote access available on an always-on machine, see [Run on a server](../advanced/server.md).
Loading
Loading