这次 Prowl 好像小小走在了 Claude Code 前面一两天,不过支持的是全 agents.. 😂 顺便也做了个宣传视频介绍了一下整个 app 的特色,暂时是满顺手了。prowl.onev.cat/
Claude Code 今天上线了一个新功能:agent view,让开发者可以在一个界面里统管所有正在运行的 AI 编程会话。
过去用 Claude Code 同时跑多个任务,只能靠一堆终端标签页和 tmux 分屏拼凑,脑子里还得记着每个任务跑到哪了。现在不用这么折腾了。
在任意会话里按左箭头,或者直接在终端跑 claude agents,就能打开 agent view 的总览界面。每一行显示一个会话的状态:在等你回复、还在跑、还是已经完成,一眼能看清。
最实用的一点是不用切换上下文就能回复。选中某个会话可以先"偷看"最新进展,如果它在等你做决定,直接在那里打回复,它就接着跑。不用打开完整会话窗口,不打断你手头在做的事。
想把某个会话扔到后台?在会话内输入 /bg。想直接起一个后台任务?claude --bg [任务描述],连前台都不用经过。
目前 agent view 以“研究预览”状态上线,Pro、Max、Team、Enterprise 和 API 用户今天就可以用,直接跑 claude agents 即可激活。
Prowl 在今天的发布中跟进支持了 OSC 7501。这对 Prowl 稳定检测 Agent 状态这一核心功能来说,是一个重要的进展。
而与之相关的其他 Agent 编排和自动化特性,比如 Agent Workflow 的派发和 Remote Mirror 等都将从这个转变中获益。
首批添加了 Claude 和 Pi 的支持,OMP/Codex/其他陆续添加 OSC 7501 支持的 agent 也会在后续更新逐渐加上。
了解详情,访问 Prowl 的 release 页面:prowl.cat/releases/
I've published a new, general-purpose terminal specification that gives any program a way to tell the terminal what it's doing: idle, working, waiting, finished, or failed, and why. It is easy to implement on both sides. I've written more about why: mitchellh.com/writing/progra…
The problem this solves is generic and applies in compelling ways to all sorts of use cases (e.g. package managers, build tools), but it really rears a hideous head when it comes to AI and the "agentic inbox" problem.
I found over 250 different agent orchestrators (with various goals) that all individually implement a heuristic based approach to detecting whether things like Claude Code are working, blocked, done, etc.
If you look at @herdrdev's commit history, you can see around 10 compatibility changes to detect Claude Code within just the past 3 months. (This isn't a dig at Herdr! They're doing great work with what they have, and everyone else is doing the same thing).
Heuristics are not the way. And over-indexing on agentic use cases isn't the way, because this problem is really interesting for other tools too: Homebrew, Terraform, Cargo, etc. etc.
Proprietary protocols and out of band APIs are not the way. They have an O(N) integration problem and require extra work to work over SSH or within local VMs/containers.
The program status specification (OSC 7501) solves this in a reliable, deterministic way that is general-purpose and can be easily adopted by the entire industry.
Read more: mitchellh.com/writing/progra…
Today’s Prowl release introduces support for OSC 7501, marking an important milestone for one of Prowl’s core features: reliable Agent status detection.
This improvement will also benefit other Agent orchestration and automation features built on top of it, such as Agent Workflow dispatching and Remote Mirror.
The initial release includes support for Claude and Pi. Support for OMP, Codex, and other Agents adopting OSC 7501 will be added gradually in future updates.
Check details: prowl.cat/releases/
I've published a new, general-purpose terminal specification that gives any program a way to tell the terminal what it's doing: idle, working, waiting, finished, or failed, and why. It is easy to implement on both sides. I've written more about why: mitchellh.com/writing/progra…
The problem this solves is generic and applies in compelling ways to all sorts of use cases (e.g. package managers, build tools), but it really rears a hideous head when it comes to AI and the "agentic inbox" problem.
I found over 250 different agent orchestrators (with various goals) that all individually implement a heuristic based approach to detecting whether things like Claude Code are working, blocked, done, etc.
If you look at @herdrdev's commit history, you can see around 10 compatibility changes to detect Claude Code within just the past 3 months. (This isn't a dig at Herdr! They're doing great work with what they have, and everyone else is doing the same thing).
Heuristics are not the way. And over-indexing on agentic use cases isn't the way, because this problem is really interesting for other tools too: Homebrew, Terraform, Cargo, etc. etc.
Proprietary protocols and out of band APIs are not the way. They have an O(N) integration problem and require extra work to work over SSH or within local VMs/containers.
The program status specification (OSC 7501) solves this in a reliable, deterministic way that is general-purpose and can be easily adopted by the entire industry.
Read more: mitchellh.com/writing/progra…
新版Prowl支持了刘海上的状态条显示,还能通过快捷键迅速打开需要关注的 agent 面板。我只用了半天,就已经形成新肌肉记忆了。大家想要试试的话,可以在Settings Agents-Display 里打开 Agent Island,并给它一个展开快捷键。我现在设了Cmd+Shift+P,感觉自己强得可怕!😎 prowl.cat/
sponsorbar.io/r/5Pu-JQkq9lZG… 过上了看广告赚美分的日子…🤣…??这神奇的想法…
有一说一,确实比原文看起来观感好多了🤣
Hey Anthropic. You guys have given me a lot of subsidized compute. In return, I'll give you an example of how to make announcements like this without burning all your good will with developers.
"Back in May, we did a one-month promotion where we increased the weekly rate limits for Claude Code by 50%. We've extended this promotion multiple times since, but sadly, it must come to an end on September 14th.
We know that this will impact the work of many users. We've run the numbers and found that we are able to make a permanent increase of 25%. This nets out to a 17% decrease from the limits as they are today.
We understand this is a big hit for a lot of users. We hate making changes like this. We're doing everything in our power to secure more compute to improve availability of Claude.
We do have some good news. When these changes go live on September 14th, we will be removing the separate weekly limit for Fable, so you will now be able to use your full limit with your preferred Claude model."
sim-use v0.14.0 is out! Physical iPhones and iPads are now supported as experimental targets 📱
`sim-use ui`, the `tap '#id'`, and screenshot can now drive a plugged-in device directly by your agent with the CLI — no test runner, no re-signing, and no Developer Disk Image required.
Physical-device support currently covers basic UI description, tapping, and screenshots, with more actions coming soon in next releases!
This release also includes countless improvements to the existing iOS Simulator and Android emulator/device support. See more in the release note.
github.com/lycorp-jp/sim-use


























