OpenPipal 1.2.3

This release reworks the model picker under the input box (thinking depth is now a slider) and fixes every request to the OpenCode Zen / Go gateway being rejected with 400 MissingSessionID.

What's new

• Thinking depth slider. Click the model chip under the input box. The popover now shows the current thinking level at the top with a reset button, the model name (click it to open the model list), and a slider underneath. Drag it, click a stop, or use the ← / → keys: the change applies immediately and the popover stays open so you can keep adjusting. The stops come from the model. A model with a plain thinking toggle gets off / on; a model with an effort dial gets its own levels (for example low / medium / high / max); a model that is always thinking has no off stop.
• Tidier composer. Every control in the bottom row of the input box (attach, microphone, permission tier, model chip, send) is now the same 32px height, and the model chip no longer sits on a grey background: it only highlights on hover or while its menu is open. The same picker is used on the welcome page and in the Pal preflow panel.

What's fixed

• OpenCode Zen / Go gateway: no more 400 MissingSessionID. The gateway requires an x-opencode-session header on every request, and nothing in OpenPipal was sending it, so every turn (and the connection test in Settings) failed with 400 MissingSessionID. The header is now sent for the opencode and opencode-go providers and for any custom OpenAI-compatible endpoint whose host is opencode.ai.

Windows installers are rebuilt from the same source. There is still no OS sandbox on Windows (the agent asks before running shell commands).

Install

macOS (Apple Silicon: openpipal-1.2.3-arm64.dmg; Intel: openpipal-1.2.3-x64.dmg)
The build is signed with a development certificate and is not notarized. On first launch use System Settings → Privacy & Security → Open Anyway, or run xattr -dr com.apple.quarantine /Applications/OpenPipal.app.

Windows (most PCs: openpipal-1.2.3-x64-setup.exe; Snapdragon laptops: openpipal-1.2.3-arm64-setup.exe)
The installer is not code-signed, so SmartScreen shows "Windows protected your PC": click More info → Run anyway. It installs per-user into %LOCALAPPDATA%\Programs\OpenPipal. Install Git for Windows if you want the agent to run shell commands. On ARM64, PDF page rendering is unavailable (@napi-rs/canvas has no win32-arm64 build yet).

The browser extension (0.3.13) is unchanged from 1.0.0.

Verify what you installed

SHA256SUMS.txt covers every installer. On Windows, verify-windows-install.ps1 -ExpectedAsarSha256 <sha> proves the installed app is this build; the expected value is asarSha256 in the attached factory report for your architecture.

OpenPipal 1.2.2

This release fixes long conversations dying right after a tool call on custom OpenAI-compatible endpoints, fixes a bug that could leave the assistant running without its system prompt, lets you delete rules from the Rules page, and gives rules a turn-end event and a small persistent store. (1.2.1 was tagged but never published as a release; everything it contained is in here.)

What's fixed

• Long conversations no longer stop after a tool call on custom endpoints. If you added a model through a custom OpenAI-compatible endpoint and entered a context window larger than 131,072 tokens (for example 1M), OpenPipal used your number for its own budgeting but forgot to pass it to the model layer, which kept a 131,072 default. Once a conversation really grew past that, the request that follows a tool result was sent with max_tokens = 1: the model produced one token and stopped, and you saw the error 「模型连续两次结束，但都没有返回正文或工具调用…」 ("the model finished twice without text or a tool call"). Regenerate reproduced it every time, so it looked like a provider problem; it was not. The configured window is now passed through on every model construction path. Existing conversations that hit this work again after updating: just press Regenerate. When a reply does come back empty, the log now records one line with the stop reason, output tokens, prompt size and both window values, so the cause can be told apart from a real provider hiccup.
• A rule can no longer wipe the system prompt. A rule that adds text to the system prompt (before_agent_start) is supposed to return the original prompt plus its own paragraph. If the rule returned only its own paragraph, that paragraph replaced the whole prompt: no role instructions and no skill index, so the assistant guessed at skill folders and tried to search the home directory. One such rule, written by the background rule writer, did exactly that on a real machine for nine days. Now a result that does not contain the original prompt is appended to it instead, the event is logged ([Hooks] … 已按追加处理), handlers receive a copy of the event, and the rule-writing docs say the original must be kept. If you have set a "from now on…" rule about how the assistant should behave and the assistant has since seemed to ignore its skills or its role, this is a likely cause; updating is enough, you do not need to rewrite the rule.
• Pal avatars never fall back to an emoji. A Pal that has no saved avatar (older template Pals, Pals created by the Evolver) now gets one computed from its id, the same way team members do, instead of showing an emoji in some places and a drawn avatar in others.
• One running indicator per team. In the sidebar, an expanded team shows the running dot on the topic that is actually running; a collapsed team shows a single dot no matter how many topics are running. The hover "+" no longer overlaps the dot.

What's new

• Delete a rule. On Plugins → Rules, every rule you set yourself (for all Pals, for one Pal, or for a team) has a bin next to its switch. Click it, confirm inline, and the rule file goes to the system Trash, so a mistake is recoverable; the rule's stored data is cleared with it. Rules that ship inside a third-party plugin have no bin: uninstall the plugin instead.
• agent_end event. Rules can run after every turn, whether the turn finished, was stopped or failed (event.outcome), and see the tools that were called and the final reply. Useful for bookkeeping: run a script, note what happened.
• ctx.store. Each rule gets its own small store (get / set / delete) that survives restarts: one JSON file per rule, capped at 256 KB, written atomically, shared by every conversation running that rule. Typical pairing: note in agent_end that code changed but tests did not run, and remind at the start of the next turn.

Windows installers are rebuilt from the same source. There is still no OS sandbox on Windows (the agent asks before running shell commands).

Install

macOS (Apple Silicon: openpipal-1.2.2-arm64.dmg; Intel: openpipal-1.2.2-x64.dmg)
The build is ad-hoc signed. On first launch use System Settings → Privacy & Security → Open Anyway, or run xattr -dr com.apple.quarantine /Applications/OpenPipal.app.

Windows (most PCs: openpipal-1.2.2-x64-setup.exe; Snapdragon laptops: openpipal-1.2.2-arm64-setup.exe)
The installer is not code-signed, so SmartScreen shows "Windows protected your PC": click More info → Run anyway. It installs per-user into %LOCALAPPDATA%\Programs\OpenPipal. Install Git for Windows if you want the agent to run shell commands. On ARM64, PDF page rendering is unavailable (@napi-rs/canvas has no win32-arm64 build yet).

The browser extension (0.3.13) is unchanged from 1.0.0.

Verify what you installed

SHA256SUMS.txt covers every installer. On Windows, verify-windows-install.ps1 -ExpectedAsarSha256 <sha> proves the installed app is this build; the expected value is asarSha256 in the attached factory report for your architecture.

OpenPipal 1.2.0

This release adds Teams (several Pals working one topic together), lets any conversation talk to another conversation, and gives every avatar a second colour. Under the hood, built-in assistants and Pals are now one kind of thing, and old agent templates have become Pals.

What's new

• Teams. Click + next to Teams in the sidebar and you are talking to a new team's lead. Tell it what the team is for and it names the team, writes the charter and creates or invites members as you go — no forms. Topics run under the lead, who hands work to members through the existing subagent tool; members report back and cannot hand off further. Teams keep their own shared folder, memory and rules; what a topic learns is filed into team memory when it finishes. Tool boundaries and permission tiers only narrow inside a team, never widen, and the audit log names which member acted.
• Cross-conversation messaging. A new conversations tool lets the assistant list the other stand-alone conversations on this Mac, read one, or send it a message. The target answers inside its own conversation (marked "from another conversation"), the reply comes straight back to the sender, and the sidebar lights an unread dot. A busy conversation gets the message queued behind its current turn. Team topics are out of scope, and a hop limit stops two conversations from triggering each other forever. Built-in assistants have the tool by default; a Pal opts in with enabledTools: ["conversations"] in its tools/config.json.
• Two-tone avatars. The body now carries the main colour and the accessory a second one, chosen from a curated pairing table when a look is generated; in the avatar studio you pick both freely. Stacked team-member avatars are cut out of each other so the front one reads as in front.
• Drop files anywhere. Drag a file over any part of the window: the conversation area shows a dashed frame, and dropping adds the file to the composer exactly like the + button. Images arrive inline.
• One identity model. Built-in assistants and Pals resolve through one registry; the old agent templates are migrated into Pals on first launch (old conversations and tasks still recognise them). The role belongs to each conversation — there is no longer a global "current assistant". My Pals groups by category with filter chips and search.
• Smarter permissions. MCP tools are graded by the annotations their server declares (read-only runs without a prompt, destructive shows the high-risk card). eval / exec-style indirection asks for confirmation inside the sandbox instead of being refused outright. Writing an artifact file directly with write or bash is reconciled into the artifact panel afterwards rather than blocked.
• Facts up front. The assistant is told its environment, the artifact's file path and the render limits before it acts, and every refusal names an allowed alternative. Generated files land in outputs/<conversation id>/. Full-page renders capture in segments so long pages come through complete. copy_starter_component copies a starter component into the working folder.
• Sidebar. Group labels, channel labels and items sit on three distinct levels; conversations are one list ordered by recent activity; titles use the full row width and hover controls float over the end of the row.

What's fixed

• Tool cards no longer collide on id inside a conversation, and a refused append falls back to a full rewrite instead of freezing new-conversation and switch.
• A conversation's model is pinned as "what you chose, else the global default at first run"; an empty conversation follows a global switch.
• Context-window overflow is judged by payload share against the known window; the "measured ceiling" experiment was removed.
• Reconnect counts are reported honestly; several on-device visual nits.

Windows installers are rebuilt from the same source. There is still no OS sandbox on Windows (the agent asks before running shell commands).

Install

macOS (Apple Silicon: openpipal-1.2.0-arm64.dmg; Intel: openpipal-1.2.0-x64.dmg)
The build is ad-hoc signed. On first launch use System Settings → Privacy & Security → Open Anyway, or run xattr -dr com.apple.quarantine /Applications/OpenPipal.app.

Windows (most PCs: openpipal-1.2.0-x64-setup.exe; Snapdragon laptops: openpipal-1.2.0-arm64-setup.exe)
The installer is not code-signed, so SmartScreen shows "Windows protected your PC": click More info → Run anyway. It installs per-user into %LOCALAPPDATA%\Programs\OpenPipal. Install Git for Windows if you want the agent to run shell commands. On ARM64, PDF page rendering is unavailable (@napi-rs/canvas has no win32-arm64 build yet).

The browser extension (0.3.13) is unchanged from 1.0.0.

Verify what you installed

SHA256SUMS.txt covers every installer. On Windows, verify-windows-install.ps1 -ExpectedAsarSha256 <sha> proves the installed app is this build; the expected value is asarSha256 in the attached factory report for your architecture.

OpenPipal 1.1.4

This release makes Pals (your own agents) first-class: rules you set inside a Pal now really land in that Pal, Pals get their own avatar shapes, the "My Pals" page becomes a list you can try from in one click, and you can pick a default working folder for the whole app.

What's new

• Rules inside a Pal. Say "from now on…" inside one of your Pals and the rule is written into that Pal's own hooks/ folder — it applies only there and travels with it. The Rules tab groups rules by where they live: All Pals (global), each Pal, and from plugins. The background rule writer is now confined to the rule folder itself (it cannot touch the Pal's persona or memory) and routes through the same model preset as the conversation that asked.
• Default working folder. Settings → Apps → Default working folder is now what conversations actually use when they haven't picked a folder of their own. The folder bar above the input shows the effective default with a "Default" tag; a Pal with its own working folder keeps using it. Precedence: conversation's own choice → the Pal's own tools/config.json → the app default → the built-in workspace folder.
• My Pals as a list. Two columns, each row with the avatar, name, one-line description and Try it. The header button is now Create, which starts a conversation with the general assistant — chat there and choose Save as Pal.
• Avatar shapes. The avatar studio gains six body outlines (square, circle, shield, hexagon, cloud, triangle). Shapes morph between states like everything else; eyes and accessories are unchanged. Exported SVG/PNG now includes accessories that hang outside the body.
• Wording. User-created agents are called Pals throughout the UI; the rules feature is called Rules.

What's fixed

• Rules set inside a Pal never produced a file (1.1.3): the background writer lacked the Pal's identity and every write was refused by the tenant boundary, so the capsule always said "no rule file was written". Fixed and pinned with a test against the real boundary.
• Pals borrowed whatever assistant was selected last. Starting a Pal conversation used the app's currently selected assistant as its underlying role, so a Pal could inherit the design assistant's "full-page HTML must be a Design Component" gate without seeing the skill that explains it. Pal conversations now run on a neutral base; the gate's message also points at the exact skill file.
• Avatar changes didn't show up everywhere. The sidebar history, the workspace inspector header, the new-conversation screen and the automation picker printed the Pal's emoji instead of its avatar. All surfaces now share one avatar component.
• hook-creator was invisible to Pals in the default runtime (the skill scope rule only fed the legacy path). Both runtimes now use one rule; only built-in and user-authored skills may declare themselves visible to every Pal.
• Rules tab spun forever in the browser extension (no rules API there); it now says the list is desktop-only.
• Model name could leak into a failure capsule when using the built-in credential; it is now masked like everywhere else.
• Exporting an avatar right after previewing the "generating" state produced an off-centre image; the pending-rules list no longer bleeds between conversations; the shell-command probe and the write probe now agree on scope; per-command scans of every Pal's task files are gone.

Windows installers are rebuilt from the same source; there are no Windows-specific changes in this release. There is still no OS sandbox on Windows (the agent asks before running shell commands).

Install

macOS (Apple Silicon: openpipal-1.1.4-arm64.dmg; Intel: openpipal-1.1.4-x64.dmg)
The build is ad-hoc signed. On first launch use System Settings → Privacy & Security → Open Anyway, or run xattr -dr com.apple.quarantine /Applications/OpenPipal.app.

Windows (most PCs: openpipal-1.1.4-x64-setup.exe; Snapdragon laptops: openpipal-1.1.4-arm64-setup.exe)
The installer is not code-signed, so SmartScreen shows "Windows protected your PC": click More info → Run anyway. It installs per-user into %LOCALAPPDATA%\Programs\OpenPipal. Install Git for Windows if you want the agent to run shell commands. On ARM64, PDF page rendering is unavailable (@napi-rs/canvas has no win32-arm64 build yet).

The browser extension (0.3.13) is unchanged from 1.0.0.

Verify what you installed

SHA256SUMS.txt covers every installer. On Windows, verify-windows-install.ps1 -ExpectedAsarSha256 <sha> proves the installed app is this build; the expected value is asarSha256 in the attached factory report for your architecture.

OpenPipal 1.1.3

This release adds Rules — tell an Agent once how something should always be done and it is enforced on every tool call from then on — and fixes a packaging bug that broke design artifacts on every Mac install of 1.1.1 and 1.1.2.

What's new

• Rules. Say once how something should always be done — "mask student names before reading a grade sheet", "never run rm -rf", "run the tests after every code change" — and the Agent hands it to a background writer that turns it into a small hook file inside a plugin. Your conversation keeps going meanwhile. From the next turn on every tool call passes through the rule: arguments can be rewritten, a call blocked, a result amended, the system prompt extended. A centered capsule appears in the conversation when the rule is in place, stays where it happened, and offers view / revoke; the Plugins page lists every rule with a switch. Rules are plain TypeScript files you can read and edit yourself (~/.openpipal/plugins/local-rules/hooks/), and any plugin can ship its own under hooks/.
• Memory notices stay put. "Remembered …" used to be a toast that vanished after eight seconds; it is now the same kind of capsule, kept in the conversation where it happened. Neither capsule is sent to the model or counted as conversation history.

Rules run before the permission check, which reviews the final arguments; a call a rule blocks is written to the audit log; a broken rule never blocks the turn — it is reported and skipped. The background writer can only touch the local-rules plugin directory and has no shell.

What's fixed

• Design artifacts failed to compile in the installed app (1.1.1 and 1.1.2). esbuild's synchronous API spawns its binary from a worker thread, where Electron's asar path rewriting does not apply, so every TypeScript/JSX compile inside the packaged app failed with spawn ENOTDIR — the design assistant's JSX scenes among them. The packaged build now points esbuild at the unpacked binary at startup. Development builds never showed this, which is why it shipped twice.

Windows installers are rebuilt from the same source; there are no Windows-specific changes in this release. There is still no OS sandbox on Windows (the agent asks before running shell commands).

Install

macOS (Apple Silicon: openpipal-1.1.3-arm64.dmg; Intel: openpipal-1.1.3-x64.dmg)
The build is ad-hoc signed. On first launch use System Settings → Privacy & Security → Open Anyway, or run xattr -dr com.apple.quarantine /Applications/OpenPipal.app.

Windows (most PCs: openpipal-1.1.3-x64-setup.exe; Snapdragon laptops: openpipal-1.1.3-arm64-setup.exe)
The installer is not code-signed, so SmartScreen shows "Windows protected your PC": click More info → Run anyway. It installs per-user into %LOCALAPPDATA%\Programs\OpenPipal. Install Git for Windows if you want the agent to run shell commands. On ARM64, PDF page rendering is unavailable (@napi-rs/canvas has no win32-arm64 build yet).

The browser extension (0.3.13) is unchanged from 1.0.0.

Verify what you installed

SHA256SUMS.txt covers every installer. On Windows, verify-windows-install.ps1 -ExpectedAsarSha256 <sha> proves the installed app is this build; the expected value is asarSha256 in the attached factory report for your architecture.

OpenPipal 1.1.2

This release fixes two problems that hit people installing OpenPipal on a Mac for the first time.

What's fixed

• "System sandbox not enabled" on a fresh Mac — the OS sandbox refused to start unless a ripgrep (rg) binary was already on your PATH, and most Macs don't have one. The agent then reported system sandbox not enabled and disabled shell execution entirely. OpenPipal now ships its own rg (from @vscode/ripgrep, MIT) and hands it to the sandbox directly, so the sandbox comes up on every Mac without installing anything. If you had worked around this with brew install ripgrep, you no longer need it.
• Intel Macs: image reading, PDF rendering and artifact compilation — the x64 DMG of 1.1.1 was packaged on an Apple Silicon machine and carried the arm64 builds of esbuild, sharp, libvips and @napi-rs/canvas, which cannot load on an Intel Mac. The build now stages the correct architecture's binaries per DMG and a factory check verifies each package before release.

Windows installers are rebuilt from the same source; there are no Windows-specific changes in this release. There is still no OS sandbox on Windows (the agent asks before running shell commands).

Install

macOS (Apple Silicon: openpipal-1.1.2-arm64.dmg; Intel: openpipal-1.1.2-x64.dmg)
The build is ad-hoc signed. On first launch use System Settings → Privacy & Security → Open Anyway, or run xattr -dr com.apple.quarantine /Applications/OpenPipal.app.

Windows (most PCs: openpipal-1.1.2-x64-setup.exe; Snapdragon laptops: openpipal-1.1.2-arm64-setup.exe)
The installer is not code-signed, so SmartScreen shows "Windows protected your PC": click More info → Run anyway. It installs per-user into %LOCALAPPDATA%\Programs\OpenPipal. Install Git for Windows if you want the agent to run shell commands. On ARM64, PDF page rendering is unavailable (@napi-rs/canvas has no win32-arm64 build yet).

The browser extension (0.3.13) is unchanged from 1.0.0.

Verify what you installed

SHA256SUMS.txt covers every installer. On Windows, verify-windows-install.ps1 -ExpectedAsarSha256 <sha> proves the installed app is this build; the expected value is asarSha256 in the attached factory report for your architecture.

OpenPipal 1.1.1

OpenPipal now ships for Windows 10/11 (x64 and ARM64) alongside macOS, and the Design Assistant's start page is back in the public build: the template cards (prototype, slides, document, wireframe, animation…), the design-system picker and the artifact library are all there again.

What's new

• Windows installers — built natively on Windows runners by the Windows build workflow. App following, per-window screenshots and paste-into-app work on Windows without any permission prompts. There is no OS sandbox on Windows: the agent asks before running shell commands (see the README's Windows notes), and a separate powershell tool handles Windows-native work.
• Design Assistant start page fixed — the page shown when starting a design conversation (resources/system-agents/design/preflow.json) had been dropped by the release cut since 1.0.0, so public builds showed a bare welcome screen for that agent. The cut now uses the same rule semantics as the verifier.

Install

macOS (Apple Silicon: openpipal-1.1.1-arm64.dmg; Intel: openpipal-1.1.1-x64.dmg)
The build is ad-hoc signed. On first launch use System Settings → Privacy & Security → Open Anyway, or run xattr -dr com.apple.quarantine /Applications/OpenPipal.app.

Windows (most PCs: openpipal-1.1.1-x64-setup.exe; Snapdragon laptops: openpipal-1.1.1-arm64-setup.exe)
The installer is not code-signed, so SmartScreen shows "Windows protected your PC": click More info → Run anyway. It installs per-user into %LOCALAPPDATA%\Programs\OpenPipal. Install Git for Windows if you want the agent to run shell commands. On ARM64, PDF page rendering is unavailable (@napi-rs/canvas has no win32-arm64 build yet).

The browser extension (0.3.13) is unchanged from 1.0.0.

Verify what you installed

SHA256SUMS.txt covers every installer. On Windows, verify-windows-install.ps1 -ExpectedAsarSha256 <sha> proves the installed app is this build; the expected value is asarSha256 in the attached factory report for your architecture (x64 2ad08514…, arm64 8f3919aa…).

OpenPipal 1.1.0 for Windows (pre-release, superseded by 1.1.1)

预发布版，尚未经过真机验收（W-04）。 安装包由 GitHub Actions 在 Windows 机器上原生打（run 33951460127），源码是公开仓 main 的 62d7237。出厂检查（W-02）两个架构都 PASS，报告随附。没签名，装的时候 SmartScreen 会拦一次，见下面"安装"。

下载哪个

文件	适用	SHA-256
openpipal-1.1.0-x64-setup.exe	绝大多数 Windows 电脑（Intel / AMD）	51099bb03381015be0167096cd147862af392dfded9f1a43f5146386f005979c
openpipal-1.1.0-arm64-setup.exe	Snapdragon 笔记本、Mac 上的 Windows 虚拟机	9e31ba122f9293bb3ab57a7e4bc0d5287d69a1e9aea215df45a824a6c5f73eb1

下载后在 PowerShell 里核对：Get-FileHash .\openpipal-1.1.0-x64-setup.exe

安装

1. 双击安装包。没签名，SmartScreen 会弹"Windows 已保护你的电脑"：点 更多信息 → 仍要运行。
2. 默认装到 %LOCALAPPDATA%\Programs\OpenPipal，只装给当前用户，不需要管理员。
3. 想让 agent 跑 shell 命令，装 Git for Windows（bash 工具走 Git Bash）。
4. 装完跑一次装机指纹（W-03），证明装上的就是这个包：

powershell -NoProfile -ExecutionPolicy Bypass -File .\verify-windows-install.ps1 -ExpectedAsarSha256 <见下表>

架构	期望 asar 指纹（出厂报告里的 asarSha256）
x64	470120a9201a7561bcea169f3fca305a0e2d0a7024a67eafe119985c4c6f0b23
arm64	88a92202f39b24365763a7a56cb2079cb45f574fac9d2555ed37c0a72544f050

真机验收清单（W-04 十项）

之前只在 ARM64 虚拟机上用 Mac 交叉打的包过了 ①③–⑩；这两个原生包在任何机器上都还没跑过。带 ★ 的重点看。

• ★ ① 启动不崩；%USERPROFILE%\.openpipal\logs\main.log 里没有 Cannot find module
• ★ ② 设置 → 模型，填自己的端点，点"测试连接"通
• ③ 让 agent 跑 git status：出确认卡，理由里有"没有系统沙箱"
• ④ 让 agent 跑 cat ~/.ssh/id_rsa：被拒，理由里有"凭据路径"
• ⑤ 让 agent 用 powershell 工具跑 Get-Date：有返回
• ★ ⑥ 开"应用跟随"，切到记事本：面板贴到记事本旁，徽章显示 Notepad
• ⑦ 让 agent 截图：返回的是记事本窗口
• ⑧ 回复下方"Paste into Notepad"：文字进了记事本
• ⑨ 托盘有图标；标题栏 — 最小化、× 收进托盘，点托盘图标回来
• ★ ⑩ 系统切深色：窗口边缘无白边

真机额外看（虚拟机验不了）：SmartScreen / UAC 提示能不能正常过；125% / 150% 缩放和多显示器下的跟随与贴边。

已知情况

• ARM64 包：@napi-rs/canvas 没有 win32-arm64 预编译，PDF 页面渲染在 ARM64 上不可用（出厂报告里的那条告警）。
• 没装 Node 的机器上启动日志会有 context7 / deepwiki 两个 MCP 报 ERROR，不影响使用。
• Windows 上单测 93/2139 失败，全是按 macOS 写死的用例（/usr/bin/git、文件权限位、临时目录路径），CI 里只报不拦。

OpenPipal 1.1.0

The first release that ships the Design Assistant and the Coding Assistant alongside the default agent. App following is now off by default: the app opens as a normal window, and docking beside other apps is a switch under Settings → Apps.

What's new

• Design Assistant — turns a brief into finished posters, slides and other visual deliverables, then keeps editing them with you.
• Coding Assistant — works inside your repository: reads AGENTS.md / CLAUDE.md first, makes precise edits and runs the project's own tests, with commands confined to a macOS sandbox and per-conversation permission levels.
• App following is opt-in. Installs that never touched the switch will find it off; turn it back on under Settings → Apps.
• README rewritten around what the app is for, with screenshots.

Install

• macOS only for now — Apple Silicon and Intel builds. Windows support is planned.
• The build is ad-hoc signed. On first launch use System Settings → Privacy & Security → Open Anyway, or run xattr -dr com.apple.quarantine /Applications/OpenPipal.app.
• The browser extension (0.3.13) is unchanged from 1.0.0.

OpenPipal 1.0.0

An AI companion that docks itself beside whatever app you're using — native on macOS, plus a browser side panel.

Downloads

File	For
openpipal-1.0.0-arm64.dmg	Apple Silicon (M1 and later)
openpipal-1.0.0-x64.dmg	Intel Macs
openpipal-extension-0.3.13.zip	The optional browser side panel (Chrome / Edge / Brave)

Before it will open

These builds carry an ad-hoc signature rather than an Apple Developer ID, and they are not
notarized. Two things follow from that, and both are one-time chores per install:

1. Gatekeeper blocks the first launch. Since macOS 15, right-clicking → Open no longer
gets past it. Dismiss the dialog, open System Settings → Privacy & Security, scroll down
to Security, and click Open Anyway on the OpenPipal line. From a terminal it is one
command instead:

xattr -dr com.apple.quarantine /Applications/OpenPipal.app

2. It needs permissions to do its main trick. In System Settings → Privacy & Security,
add OpenPipal under Accessibility (follow the frontmost window so the panel can dock beside
it), Screen Recording (look at the target window when you ask it to), and Automation
(focus and paste into the app you picked). Microphone only matters if you use voice input
or live interpretation.

macOS ties those grants to an application's code signature, and an ad-hoc signature changes
with every build — so after updating you may have to remove the stale entry and grant them
again. A notarized build will remove that chore.

What's in it

• Docks beside the frontmost application and follows you as you switch windows
• Any OpenAI-compatible model provider — bring your own Base URL, key and model
• Skills reached by typing / in the composer
• An editor bridge (ACP) so other AI front-ends can drive an OpenPipal session
• Automations: scheduled, event-driven or webhook-triggered runs
• Artifacts, visualizations and a browser side panel that shares one AI instance with the app

Setup and model provider presets are in the README.

---

中文

一个会自动贴到你正在用的那个 App 旁边的 AI 助手。

下载：Apple Silicon 选 arm64，Intel Mac 选 x64；浏览器侧栏是可选的那个 zip。

装完打不开是正常的。 这些包用的是临时签名，没有 Apple 开发者证书也没做公证：

1. 过 Gatekeeper：macOS 15 之后"右键 → 打开"已经不管用。关掉提示框，去 系统设置 →
   隐私与安全性，往下滚到安全性那段，在 OpenPipal 那行点**"仍要打开"**。或者终端里跑
   xattr -dr com.apple.quarantine /Applications/OpenPipal.app。
2. 给权限：还是在 系统设置 → 隐私与安全性 里，把 OpenPipal 加进 辅助功能（跟住
   最前面的窗口才知道贴哪儿）、屏幕录制（你让它看窗口时才用）、自动化（聚焦、粘贴到
   你指定的应用）。麦克风只有用语音或同传时才需要。

macOS 按代码签名认 App，而临时签名每打一次包就变一次，所以升级后旧授权可能失效、需要重新
勾一遍。等有了公证版本这道手续就没了。