与「Thread」相关的搜索结果

My laptop has become a “satellite device” since I started using Codex from my phone. And my Mac mini has become the “home.” It’s clunky, but the end state feels more like how we’re going to be working in the near future: I’m currently running the Codex app on 2 devices: 1. my MacBook 2. my Mac mini My laptop isn’t reliably connected to Wi-Fi enough, so I keep a Mac mini on my desk that is always connected. When I kick off new threads from my phone, I start them on the Mac mini. When I’m working from my desk, I run them there too. The cool part is that I’ve added my MacBook and Mac mini as connected devices to each other. That means I can start and resume threads from either device. So if I’m in a meeting but want to continue a thread on my laptop that was started on my Mac mini, I can do that. I’ve also set up mutual SSH for Mac mini <> MacBook, so files are easy to access from either side. It’s not fully seamless yet, but the model works. What this means: - I have an always-on Codex that is accessible from my phone, with its own dev environment - All threads are always accessible from any of the 3 devices - I can run heartbeat threads that stay on 24/7 It’s a little makeshift today, but the shape of it feels very real to me: Codex is no longer tied to whichever computer happens to be open in front of me. It starts to feel like something I can stay connected to across whatever device I’m using.

OpenCLI 一键打通 Agent 的 Twitter 世界！🚀 发推、回复、引用转推、监控通知、关键词触发自动回 DM、把整条 thread 抓下来总结、批量整理 list、定期备份某个人的所有图和视频——你想到的客户端操作，Agent 都能替你跑。 不需要 X API key。不需要等审批。不用 OAuth 折腾半天。 全部复用浏览器登录态——你能在网页上做的事，Agent 都能做。 OpenCLI 的 Twitter 适配器膨胀到 36 个命令，几乎打穿整个客户端： 读：timeline / search / thread / tweets / likes / followers / following / bookmarks / notifications / trending / article / download 写：post / reply / quote / retweet / like / bookmark / follow / block / hide-reply / delete DM：reply-dm / accept 关键词自动放行 List：lists / list-tweets / list-add / list-remove 以前 Agent 看 Twitter 只能爬时间线 现在 search → thread 抓完整讨论 → 总结 → quote / reply 发出去，一条流水线串到底 Twitter 是 Agent 的第一个完整生活场景。

parameter golf was a blast. 2,000+ submissions. 1,000+ verified github accounts. ideas ranging from quantization and depth recurrence to TTT LoRA, SSMs, H-nets, JEPA, and more. autoresearch made iteration dramatically faster — and led to emergent bulletin boards, issue threads, unofficial leaderboards, and agent-built writeups that helped everyone learn from everyone else. it felt like a glimpse of where interaction with AI is headed: humans setting taste and direction, agents helping explore, coordinate, and share what works. our goal was simple: make ml research accessible to anyone, anywhere. it was amazing to see that happen. full recap: future events:

1/ 🔐 Firefox刚修了423个安全漏洞。 不是一年。是2026年4月，一个月。 2025年全年，每月平均修20个。 这不是团队突然变强了。 是AI第一次真正学会了找漏洞。 一个Thread讲清楚👇

Snap CEO Evan Spiegel的这个访谈，对AI消费类产品创业公司应该会有所启发 -当软件并非护城河时，如何才能赢得胜利？ -Snapchat 是过去 15 年里少数真正活下来的消费级社交产品，拥有接近十亿月活用户，年收入超过 60 亿美元 -为什么做一个持久的消费级社交产品这么难？Evan 的答案不是“体验够不够好”，而是落在产品的分发。TikTok 和 Threads 之所以是少数新近成功案例，在他看来不是因为它们只找到了产品市场匹配，而是都解决了冷启动分发 -TikTok 用巨额资金同时补贴观看者和创作者，Threads 借用了 Meta 已有产品的巨大流量 -AI 会让做产品、写代码、想策略都变容易，但它不会自动帮你拿到用户注意力。当供给爆炸时，用户愿意试用、愿意留下、愿意分享，反而成了更稀缺的能力 -"消费科技里，很多人都在问是不是做对了产品、有没有产品市场匹配，但人们花在思考分发、弄清分发上的时间远远不够。" -社交网络的价值，不是连接更多人 -"真正重要的不是把你连接到所有朋友，而是把你连接到最好的朋友、伴侣、配偶，以及世界上你最在乎的人。" -对今天的产品经理来说，这个判断同样适用：不要只问“我的网络能不能更大”，还要问“我解决的是不是用户最真实、最高频、最愿意保留的关系”。 -创新不是灵感，是每周几百个想法 访谈原视频：

App Wave 2 is now live on Terminal More ways to engage with apps across gaming, DeFi, and DePin. We've also allowed users to reset their boosted apps if they wish to re-allocate to the new group. The Apps [thread]

ran a codex session yesterday. closed the laptop at minute 57. came back 5.5 hours later. /goal had already resumed on its own. it injected its own developer message ("Continue working toward the active thread goal") and kept going. no re-prompt. no recovery steps. i opened the lid and it was four turns in. the full session: 6h 44min wall time, ~41 min actual model compute. 6.8M cumulative input tokens at 94% cache hit. final status TASK_COMPLETE. all four target end-to-end test scenarios passed. this is /goal in codex v0.128.0. it's the ralph loop, made first-class. native persistence, runtime continuation, tui controls. the goal survives sleeps, network drops, deliberate pauses. you don't have to be there. what surprised me: the prompt is the contract. mine was 600+ words. structured xml blocks, a reading list, working rules, anti-pattern fences, a done_when block. "/goal do thing" is not the interface. the prompt is. would love to hear what you think.