Keep on to blur preview images; turn off to show them clearly
今天起来发现青萍空气质量检测仪Lite离线了，之前是24小时连接电源线的状态。 看到它黑屏了，无法再次开机，摸着还能感觉到微微发热。凑近闻了一下还有奇怪的味道，但表面看不到异样，可能是主板烧掉了（不是锂电池就好）。 看了下订单记录差一个月就过保了，于是赶紧联系了客服。
去年是因为给车换 HEPA 滤芯，想了解换滤芯前后是否真的有效果才买的这个检测仪（谁叫 Tesla 把相关的传感器成本给省了）。 后来我用它测了很多环境里的空气质量和清新程度（比如高铁、飞机上的 CO2 浓度），不敢说很精确，但至少是很有参考价值的。这个过程给我带来了一点乐趣，也带来了一些焦虑（过度关注各种数据带来的负面影响）。 总的来说，当个实用工具偶尔玩玩挺好，但没必要过度关注。 https://t.co/8lyk3TuXNH
RT @indie_maker_fox: 🎉 MkSaaS模板的双十一和黑五活动来啦 🥳 价格回到半年前发布时的价格 $169，活动持续到月底 感兴趣的朋友可以入手啦，或者进入 discord 免费抽奖 抽奖完全随机，双十一当天开奖，老客户若抽中就退款 https://…
🚀 The best AI SaaS boilerplate - https://t.co/VyNtTs0jSX 🔥 The best directory boilerplate with AI - https://t.co/wEvJ1Dd8aR 🎉 https://t.co/zubXJCoY92 & https://t.co/tfQf8T7gGF & https://t.co/TqRkfQj41f
RT @indie_maker_fox: 🎉 MkSaaS 模板新案例 — Image to Sketch 利用AI一键将图片变成手绘插画，适合创作者、教师等人群 网址：https://t.co/fBl8wltnrJ 整个网站很有设计，简单朴素，没有花里胡哨，真不错 👍…
🚀 The best AI SaaS boilerplate - https://t.co/VyNtTs0jSX 🔥 The best directory boilerplate with AI - https://t.co/wEvJ1Dd8aR 🎉 https://t.co/zubXJCoY92 & https://t.co/tfQf8T7gGF & https://t.co/TqRkfQj41f
我去，什么原理，我全对
脚踏实地做梦/独立开发/降临派/新手奶爸👨🍼
This tip closes the automation loop completely; I learned it after I recorded the video above:
Former Quant Investor, now building @lumera (formerly called Pastel Network) | My Open Source Projects: https://t.co/9qbOCDlaqM
I just figured out how to really automate my agent workflow even more with some tmux wizardry. Now that I'm using my mcp agent mail project to get a bunch of agents to talk to each other about implementing a plan (and also coordinating using the beads project for task management), I still need to "feed" the agents by queueing up a bunch of messages in codex to keep them busy. This involves going one by one through the various tmux panes (one for each codex instance) and pasting in some canned messages or hitting the up arrow a few times to reuse past messages, such as: "Pick the next bead you can actually do usefully now and start coding on it immediately; communicate what you're doing to the other agents via agent mail." It feels a bit silly and inefficient to be doing this, even though it doesn't take that long to give each agent enough instructions to keep them busy for over an hour. But now I realized I can automatically queue up a bunch of messages in every relevant tmux pane at once, simply by copying and pasting this into the console outside of the tmux session (this is tested and working in zsh): --- PANES=(${(f)"$(tmux list-panes -a -F '#S:#I.#P' | tail -n +3 | head -n -2)"}) for pane in $PANES; do tmux send-keys -t $pane -l 'pick the next bead you can actually do usefully now and start coding on it immediately; communicate what you'"'"'re doing to the other agents via agent mail.' sleep 0.1 tmux send-keys -t $pane Enter for i in {1..4}; do tmux send-keys -t $pane -l 'keep going, doing useful work! and communicate!' sleep 0.1 tmux send-keys -t $pane Enter done tmux send-keys -t $pane -l 'great, now I want you to carefully read over all of the new code you just wrote and other existing code you just modified with "fresh eyes" looking super carefully for any obvious bugs, errors, problems, issues, confusion, etc.' sleep 0.1 tmux send-keys -t $pane Enter tmux send-keys -t $pane -l 'Be sure to check your agent mail and to promptly respond if needed to any messages; thereafter proceed meticulously with the plan, doing all of your remaining unfinished tasks systematically and continuing to notate your progress in-line in the plan document, via beads, and via agent mail messages. Don'"'"'t get stuck in "communication purgatory" where nothing is getting done; be proactive about starting tasks that need to be done, but inform your fellow agents via messages when you do so and notate that in-line in the plan document. When you'"'"'re really not sure what to do, pick the next bead that you can usefully work on and get started.' sleep 0.1 tmux send-keys -t $pane Enter tmux send-keys -t $pane -l 'ok can you now turn your attention to reviewing the code written by your fellow agents and checking for any issues, bugs, errors, problems, inefficiencies, security problems, reliability issues, etc. and carefully diagnose their underlying root causes using first-principle analysis and thereafter fix or revise them if necessary? Dont restrict yourself to the latest commits, cast a wider net and go super deep!' sleep 0.1 tmux send-keys -t $pane Enter done --- This script: Gets panes: Finds all tmux panes, excluding the first 2 and last 2 Sends 8 messages to each selected pane: "pick the next bead..." - tells agents to start working on next task "keep going..." × 4 - repeated encouragement to continue working "carefully read over..." - instructs fresh code review "check agent mail..." - long message about coordination, avoiding communication paralysis, staying productive "review code written by fellow agents..." - peer code review for bugs/issues Each message is sent literally (-l flag) with a 0.1 second delay before Enter to ensure the Codex CLI processes them properly.
Actually, this is a better way to do it, by filtering on the name of the pane (in my case, it's "node" for the codex panes), and it has the initial 0.1 second sleep, without which it skips the first matching pane without sending the messages correctly: PANES=(${(f)"$(tmux list-panes -a -F '#S:#I.#P #{pane_current_command}' | rg ' node$' | cut -d' ' -f1)"}) for pane in $PANES; do sleep 0.1 # Initial sleep to ensure pane is ready tmux send-keys -t $pane -l 'pick the next bead you can actually do usefully now and start coding on it immediately; communicate what you'"'"'re doing to the other agents via agent mail.' sleep 0.1 tmux send-keys -t $pane Enter for i in {1..4}; do tmux send-keys -t $pane -l 'keep going, doing useful work! and communicate!' sleep 0.1 tmux send-keys -t $pane Enter done tmux send-keys -t $pane -l 'great, now I want you to carefully read over all of the new code you just wrote and other existing code you just modified with "fresh eyes" looking super carefully for any obvious bugs, errors, problems, issues, confusion, etc.' sleep 0.1 tmux send-keys -t $pane Enter tmux send-keys -t $pane -l 'Be sure to check your agent mail and to promptly respond if needed to any messages; thereafter proceed meticulously with the plan, doing all of your remaining unfinished tasks systematically and continuing to notate your progress in-line in the plan document, via beads, and via agent mail messages. Don'"'"'t get stuck in "communication purgatory" where nothing is getting done; be proactive about starting tasks that need to be done, but inform your fellow agents via messages when you do so and notate that in-line in the plan document. When you'"'"'re really not sure what to do, pick the next bead that you can usefully work on and get started.' sleep 0.1 tmux send-keys -t $pane Enter tmux send-keys -t $pane -l 'ok can you now turn your attention to reviewing the code written by your fellow agents and checking for any issues, bugs, errors, problems, inefficiencies, security problems, reliability issues, etc. and carefully diagnose their underlying root causes using first-principle analysis and thereafter fix or revise them if necessary? Dont restrict yourself to the latest commits, cast a wider net and go super deep!' sleep 0.1 tmux send-keys -t $pane Enter done