按照建议改了3、4、5,另外worktree清理也可以设置一下
Delete merged worktrees
Delete inactive worktrees
Delete settled worktrees
inactive和settled我都设置了8天,这样就可以及时自动清理了,空间不至于膨胀的太多
T3 Code 几个很棒的设置,建议打开,暂时不用也可以点个收藏噢!
1. 新项目默认位置:Settings -> Threads -> Add project starts in,Windows 可以修改成 D 盘等,否则默认在 C 盘
2. 允许连接其他设备:Settings -> Labs -> Linked enviroments 允许 Agent 在其他设备接力
3. 额度恢复时继续会话:Settings -> Threads -> Resume after usage limits
4. 自动恢复会话: Settings → Maintenance → Continue threads after restarts 重启或者崩溃后,自动帮你continue 对话
5. 手机接收通知: Settings → Sharing & access → Publish agent activity 打开
6. 把 T3 Code 当成 MCP 使用:Settings → Sharing & access 底部的 Authorized clients 点击 “Use in another app (MCP)”
t3.codes/
1
38
现在手机和 MacBook 都能连回家里的 Mac mini,用上面跑着的 Claude Code。用的就是 T3 Code + Tailscale,美滋滋啊,随时Coding
之前换了几种没有找到最佳姿势,或者是感觉用起来很不习惯,或者说“手感”那没那么好
我想解决的事情其实很简单:Claude Code 跑在家里的 Mac mini 上,我在其他电脑、手机上也能接着用,会话可以继续
之前用 Orca,编排这块确实不错。但我现在用Opus5.5感觉用不上那么重的编排了,更在意日常操作顺不顺手。
T3 的界面、交互,还有手机上的适配,都很不错,并且每个会话也能选不同模型
然后再配合搭配上 Tailscale,就更加丝滑了~ 这是一个可以多个设备组网的工具。之前一直误解它😂
以前用起来很卡,一段一段的,还经常断开,拿 Codex 修过也没修好。这次在 Mac mini 上才找到原因:Clash 和 Tailscale 抢 DNS!
还在继续用,看看 T3 有什么“摩擦”的地方,至少现在很舒服,大家有什么更好的方案一起讨论呀~
1
201
我的也解封了,3年老号回归,天才程序员继续上线,现在有2个Max号了
申诉的人设写的是: 在美国和英国做AI行业的中国人身份,没有违反任何条款!如果有检查到中国IP是因为国内的App等应用需要中国IP访问导致的。
不过经过这次,已经把Claude封号看淡了,死了就换新,老号情感彻底割舍,就好像买来的新车“终于”出了一次事故,以后彻底不紧绷了
这两天鼓捣了新的coding方案,T3Code配合tailscale,太舒服了😌
从这次结果来看,要感谢这次封号事件,收获不少啊
来吧,国人的方法是封不完的!下午又整了一个
用的是CCBaga的这个方案,把原账号原痕迹都清理一下,然后把颜色全绿了,就可以继续注册了
注册后使用一忽儿,就给你弹订阅,随后就跳一次KYC,但是这次和 Portal 那次不一样,
这个时候用我们护照+真人是可以的,记得用手机扫电脑二维码的时候,手机环境需要同IP + 同时区 + 英文语言,否则会有问题
看看这次会坚持多久把!同时也要看看我们梁圣DSH的方案架构了,梁圣才是光明大道啊
github.com/liseami/CCBaga
1
16
2,046
二歪2y retweeted
AI made it so anyone can build anything, but everyone was already distracted, so AI just made it 10x worse. Your competition was non existent to begin with, and your only real competition is your own mind.
二歪2y retweeted
🔍 Search & Fetch APIs are now open to everyone!
Powered by our in-house search engine, serving hundreds of millions of requests daily worldwide.
💰 Each endpoint: $0.75 per 1,000 calls.
📖 Docs: api-docs.deepseek.com/guides…
📌 Search & Fetch calls via server-side tools in DeepSeek Harness, Claude Code, and Codex are currently free for DeepSeek API users. Billing starts Oct 31, 2026, at 16:00 UTC.
3/4
二歪2y retweeted
Something I have been thinking about: in the past, the best engineers I knew spent a lot of time automating their work in various ways. Better vim/emacs automations, writing lint rules to catch repeat code issues, building up a suite of e2e tests so they don't need to smoke test the app manually. These kinds of things were the highest leverage activities an engineer could do, because it multiplied their own output, which in turn meant they could build more things.
I think many of these automations have become even more important now. This is true for a number of reasons.
First, infra and DevX automation speeds you up. And if you are running an army of agents, each of those agents will be sped up also. More automation == more output per unit of time.
Second, moving things to code improves efficiency. Your agent could fix an issue every time it sees that issue happen, but that uses tokens and might miss cases. If Claude instead writes a lint rule, CI step, or routine, that class of issue can be fully automated forever. This is really what people are talking about when they talk about loops -- it's about automating entire types of busywork rather than solving them one off. This isn't a new idea at all. Engineers have been doing this for a long time!
Third and most importantly, automation makes it possible for others to contribute to the codebase more easily. Increasingly what I am seeing is engineers are contributing to codebases on day one because Claude can navigate the codebase for them, and that non-engineers are able to contribute to a codebase as effectively as engineers can. What gets in the way of both of these is domain knowledge that lives in peoples' heads rather than in automation -- the stuff you used to have to learn when ramping up. What has changed thanks to agents is the domain knowledge that can be encoded as infrastructure is no longer limited to what is expressible in lint rules and types and tests; it can now capture nearly all domain knowledge, encoded as code comments and skills and CLAUDE.md rules and memories. If I put up a PR for an iOS codebase I don't know and a code reviewer rejects it because it doesn't use the right framework, or if a designer builds a new feature and it gets rejected because it doesn't follow the right architectural patterns, these are failures of automation.
Every team should be writing the CLAUDE.md's, REVIEW.md's, skills, and docs that enable agents to productively work in their codebase with zero additional context from the prompter. This sounds crazy, and at the same time is a natural extension of the stuff engineers have always done: automate, and encode domain knowledge as infrastructure. As the model gets smarter and as the harness matures, this task becomes easier. In the meantime, it is on every team to look for ways to convert their domain knowledge to infra so that Claude can write code better, so that code review catches issues automatically, and so the next person working on your codebase can contribute more easily.
二歪2y retweeted
Morning. The last 48 hours of Codex and ChatGPT Work have been intense! Three important updates:
- Temporarily removing the 5 hour usage limit restriction for all Plus, Business and Pro plans
- Rolling out changes that will make GPT 5.6 Sol more efficient across the board and that will be reflected in less usage being used so that it can take you further. Exact impact to be quantified and shared
- We hit 6M active users, and are landing a usage reset in the next hour
Go do things






















