Skip to content

Yew Harness 1.7.0

Choose a tag to compare

@dozybot001 dozybot001 released this 18 Nov 16:59
· 86 commits to main since this release

新增

  • 联网搜索自带:有 DeepSeek 的密钥就能搜,用的是 DeepSeek 官方的搜索接口,不用另配;搜索词发给 DeepSeek,费用记在你的 DeepSeek 账上。存了博查、Tavily 或 Brave 的密钥时先用它们。
  • hooks:写法和 Claude Code 的一样,在数据目录的 hooks.json 里配。支持会话开始、你发消息时、工具调用前、工具调用后、会话停下前五个时候:命令从标准输入收到这一刻的 JSON,返回码 2 能拦下这一步,会话开始和发消息时打印的内容交给会话。hooks 不能替你放行,也不能替你批审批;项目仓库里带的 hooks 不读。
  • 授权方式改成默认、自动、跳过三种,只管「这一步能不能执行」;只有你能定的事(对外发布、以你的名义对外发消息、往外发数据、远程主机和生产环境、删工作区外的文件、提高花费上限)叫审批,三种方式下都在审批中心等你决定。
    • 默认:原来的按需授权。常用的操作直接执行,有风险的(推送、删工作区里的文件、在沙箱外运行、连没放行的网站等)先问你。
    • 自动:本来要问你的,先交给一次单独的模型检查,它只看你在这个会话里亲自写的话、会话的职责和这一步;判断是你要它做的就直接执行,记录里标「自动放行」和理由,否则再问你。这次检查用会话自己的模型,费用记在这个会话上。
    • 跳过:什么都不问,定时任务里也一样;有风险的在记录里标「有风险」和原因,任务列表里用跳过方式跑的任务标「跳过方式」。碰 Yew Harness 自己的数据、用它的命令行和碰「会话读不到的目录」的命令照样问你,免得会话替你做了决定。审批只拦得住命令和工具里看得出来的对外操作,脚本里发出去的看不出来。
    • 在沙箱外跑的命令也有一层外层保护:读写不了 Yew Harness 的数据目录和 Mac 应用存登录状态的地方,拉不起保护之外的程序(open、osascript 叫别的程序),写不了之后会自己运行的启动文件、git 和 ssh 的设置、仓库的钩子和设置;别的都不拦。所以 git init、git clone、git remote add、git config 和 open -a 这类要你自己做。会话要在浏览器里打开网址时用新的 open_url 工具,在你的默认浏览器里打开。这层保护起不来时,在沙箱外运行三种方式下都要你决定。
    • 电脑操控跟着授权方式走:默认方式下每一步都问,跳过方式下不问。跳过方式下它能点到屏幕上的任何东西,包括 Yew Harness 里等你批准的按钮,所以用跳过方式时请停用它,或留意它在做什么。
  • macOS 上 yew app install(和设置「启动」里的同一个开关)装的是有自己窗口的 Yew Harness 应用,不再打开浏览器:Dock 上有图标,角标是审批中心里等着的件数;菜单栏有关于、设置(⌘,)、编辑、显示(重新载入、缩放、全屏幕)和窗口。打开时 Yew Harness 没在运行就先在后台启动它,再自动登录。关掉窗口应用不退出,点 Dock 图标回来;退出应用也不停 Yew Harness,会话照常在后台运行。窗口里只打开 Yew Harness 自己的页面,消息里的链接、官网和 MCP 服务的登录在默认浏览器里打开;导出这类下载会弹保存框,只保存 Yew Harness 自己的文件,保存的文件带隔离属性,打开前 macOS 会先检查。系统沙箱里的命令读写不了这个应用的登录 Cookie 和缓存。已经装过图标的,再运行一次 yew app install 换成新应用。

变更

  • 原来的「逐项授权」去掉了,用它的会话和定时任务改成默认方式;「按需授权」改叫默认,「完全授权」改叫跳过。
  • 自带的浏览器默认用你自己的 Chrome,用你在 Chrome 里已有的登录。先在 Chrome 应用商店装上「Playwright Extension」扩展;会话第一次用浏览器时,Chrome 打开一页请你同意连接,并选给它用的标签页或标签页分组,之后它只碰这些标签页和它自己开的标签页。它改不了 Cookie 和网站权限这类整个浏览器的设置;在网页里运行脚本时,能读到这个网站允许脚本读取的 Cookie;它下载的文件进你自己的下载文件夹。点击、输入、打开网址,以及后退、切换或关闭标签页、改窗口大小这类会动页面和标签页的操作,默认方式下每次都要你确认,不能选「总是允许」,以前记住的也不算,只有看页面、截图这类纯读取的可以记住;共享的标签页里有开着 Yew Harness 的,浏览器工具一律不执行,等你把那个标签页拿出来。设置的「MCP 服务」里,浏览器一行可以改回「单独的窗口」,改了马上生效;单独窗口里的操作仍可以选「总是允许」。
  • 隐私政策更新到 2.7:写明自带的浏览器默认用你自己的 Chrome,资料留在 Chrome 里;用你自己的 Chrome 时,会话能在你选给它的和它自己开的标签页里打开你已登录的网站、读取页面内容,在页面里运行脚本时还能读到这个网站允许脚本读取的 Cookie,这些会发给模型服务商;浏览器在页面上的操作(点击、输入、打开网址、运行脚本等)不能选「总是允许」;以及怎样断开它和 Chrome 的连接;还写明用 Mac 应用打开界面时,macOS 在 ~/Library 里替它存的登录 Cookie、界面文件的缓存、几项本地设置和窗口位置(不含会话内容),以及怎样删除;三种授权方式下各问什么,自动方式的检查会把你写的话、会话的职责和这一步发给服务商,跳过方式下电脑操控能替你点下审批;联网搜索时搜索词发给哪家服务;hooks 会收到什么、输出发往哪里。用户协议同样写明三种授权方式和跳过方式下电脑操控的例外。

安全

  • 自带的浏览器不再提供 browser_run_code_unsafe:它在浏览器服务自己的进程里执行任意代码,而这个进程不在系统沙箱里,批准一次就等于让会话在沙箱外跑代码。会话硬要调用也会被拒绝。读写 Cookie 和网页存储的浏览器工具也不提供,浏览器服务给了也会滤掉。
  • 浏览器的调用里带 Yew Harness 自己的地址时不执行。

手机端

  • 安卓版 Yew-1.7.0.apk:和 1.6.0 相比,应用里的隐私政策和用户协议更新到 2.7。签名证书没有变,SHA-256 指纹是 9F:F5:6E:EA:A8:3C:DC:01:BA:66:D8:79:23:9C:DE:5A:2A:69:C3:AE:D2:60:5C:D8:E1:B9:34:8D:BF:28:61:B2。安装包从提交 a10bf09 构建,也就是标签 v1.7.0 指向的提交。
  • 安装包 Yew-1.7.0.apk 的 SHA-256:e9253b35e15af33f3270c7dac0ff346e8eb8a353d55ef4062c3c30dd5b9fb28f,和附件 SHA256SUMS 一致。
  • iPhone 版之后经 App Store 发布。

电脑端:npm install -g @tenonai/yew。Linux 上的系统沙箱要先装 bubblewrap、socat 和 ripgrep。


English

Added

  • Built-in web search: with a DeepSeek key, sessions search the web through DeepSeek's official Search API, with nothing more to set up; the query goes to DeepSeek and each search is charged to your DeepSeek account. A key you saved for Bocha, Tavily or Brave is used first.
  • Hooks, written the way Claude Code's are, in hooks.json in the data folder. Five points: when a session starts, when you send a message, before and after a tool call, and before a session stops. A command gets the moment as JSON on standard input; exit code 2 stops the step, and what it prints at session start and on your messages goes to the session. Hooks cannot allow anything or answer a decision for you; hooks in a project's own files are not read.
  • Permission modes are now Default, Auto and Skip, and they only govern whether a step may run. What only you can decide (publishing, messages to others in your name, sending data out, remote machines and production systems, deleting outside the workspace, raising spending limits) is a decision, and waits for you in the approval center in every mode.
    • Default, formerly "Ask when needed": common operations run; risky ones (pushing, deleting in the workspace, running outside the sandbox, reaching unlisted sites and the like) ask first.
    • Auto: what would be asked goes first to a separate check by the session's own model, which sees only what you wrote in that session, the session's role and the step. When it finds that you asked for the step, the step runs and its row says "allowed by the check" with the reason; otherwise you are asked. The check is charged to that session.
    • Skip: nothing is asked, scheduled runs included; risky calls are marked "risky" with the reason, and scheduled tasks that run in Skip are tagged. Commands that touch Yew Harness's own data, use its command line or touch a folder you keep from sessions still ask, so a session cannot decide in your place. Decisions only catch outward actions Yew Harness can see in a command or tool; one a script sends cannot be seen.
    • Commands that run outside the sandbox now run in an outer guard: they cannot read or write Yew Harness's data folder or where the Mac app keeps its sign-in, cannot start programs outside the guard (open, osascript telling another program), and cannot write what later runs by itself (start-up files, git's and ssh's settings, repositories' hooks and settings); nothing else is closed. So git init, git clone, git remote add, git config and open -a are yours to run. To open an address in a browser, sessions use the new open_url tool, which opens it in your default browser. Where the guard cannot start, running outside the sandbox is your decision in every mode.
    • Computer control follows the mode: every step asks in Default and none in Skip. In Skip it can click anything on the screen, including Yew Harness's approval buttons, so turn it off or keep an eye on it when you use Skip.
  • On macOS, yew app install (and the same switch under Startup in the settings) installs a Yew Harness app with a window of its own instead of opening the browser: an icon in the Dock with the approval center's count, and menus for About, Settings (⌘,), Edit, View (Reload, zoom, full screen) and Window. It starts Yew Harness in the background if needed and signs in. Closing the window keeps the app, quitting the app keeps Yew Harness and its sessions running. Only Yew Harness's own pages open in the window; links, the website and MCP sign-ins open in your default browser; downloads ask where to save, only Yew Harness's own files are saved, and saved files carry the quarantine mark. Commands in the system sandbox cannot read or write the app's sign-in cookie and cache. If you installed the old icon, run yew app install again.

Changed

  • "Ask each time" is gone; sessions and scheduled tasks that used it now use Default. "Ask when needed" is now Default, and "Full access" is now Skip.
  • The built-in browser uses your own Chrome by default, with your sign-ins there. Install "Playwright Extension" from the Chrome Web Store; the first time a session uses the browser, Chrome opens a page where you approve the connection and choose the tabs or tab group it may use, and it touches only those and the tabs it opens. It cannot change browser-wide settings such as cookies and site permissions; a script it runs in a page can read the cookies that site lets scripts read; its downloads go to your own Downloads folder. In Default, actions on pages and tabs (clicking, typing, opening addresses, going back, switching or closing tabs, resizing the window and the like) ask every time and cannot be set to Always allow; only reading, such as page snapshots and screenshots, can be remembered. While a shared tab has Yew Harness open, browser tools do not run. Under MCP servers in the settings, the browser can be switched back to a separate window at once; actions there can still be set to Always allow.
  • The privacy policy and terms are now 2.7: the built-in browser using your own Chrome and what a session can read there; what macOS keeps in ~/Library for the Mac app and how to delete it; what each permission mode asks, what the Auto check sends to the provider, and that computer control can click approvals in Skip; where search queries go; what hooks receive and where their output goes.

Security

  • The built-in browser no longer offers browser_run_code_unsafe, which runs arbitrary code in the browser server's own process, outside the system sandbox; a session that calls it anyway is refused. Browser tools that read or write cookies and page storage are not offered either.
  • A browser call that names Yew Harness's own address does not run.

Phones

  • Android Yew-1.7.0.apk: compared with 1.6.0, the privacy policy and terms in the app are 2.7. The signing certificate is unchanged; its SHA-256 fingerprint is 9F:F5:6E:EA:A8:3C:DC:01:BA:66:D8:79:23:9C:DE:5A:2A:69:C3:AE:D2:60:5C:D8:E1:B9:34:8D:BF:28:61:B2. The package was built from commit a10bf09, the one tag v1.7.0 points to.
  • SHA-256 of Yew-1.7.0.apk: e9253b35e15af33f3270c7dac0ff346e8eb8a353d55ef4062c3c30dd5b9fb28f, as in the attached SHA256SUMS.
  • The iPhone app will come through the App Store.

On the computer: npm install -g @tenonai/yew. On Linux, install bubblewrap, socat and ripgrep for the system sandbox.