
陈成
1.4K posts

陈成
@chenchengpro
engineering @antgroup, created umijs, dvajs, mako and neovate code




锁定访问权限:
/telegram:access policy allowlist
具体的操作方式 - Discord:
创建 Discord Bot 并加进自己的服务器
▫ 去  → New Application
▫ 创建 Bot,点「Reset Token」拿到 token
▫ 在 Bot 设置里打开 Message Content Intent
▫ 在 OAuth2 → URL Generator 里勾选 `bot`
▫ 然后给它这些权限:View Channels / Send Messages / Send Messages in Threads / Read Message History / Attach Files / Add Reactions
▫ 打开生成的链接,把 bot 邀请进自己的服务器
安装插件:
/plugin install discord@claude-plugins-official
配置 Token:
/discord:configure
命令启动 ClaudeCode:
claude --channels plugin:discord@claude-plugins-official
配对 Discord 机器人:
私信你的机器人发配对码;
回到 Claude Code 发:
/discord:access pair <配对码>
/discord:access policy allowlist 
Claude Code 推出了官方可以远程连接 Telegram 和 discord 的 MCP 直接设置就可以用手机远程控制 CC


We just released Claude Code channels, which allows you to control your Claude Code session through select MCPs, starting with Telegram and Discord. Use this to message Claude Code directly from your phone.


An uncomfortable truth about building agents/models: By default, your most lucrative, most-smitten customers will be those using intricate out-of-band techniques that are exorbitantly expensive and probably net negative (but that they love). It's a very weird incentive. You can't and don't want to indulge this. There's nothing wrong with experimentation, but if you saw what every agent company sees, you'd know this goes way beyond experimentation. Amp tries really hard to prevent this: limiting long context, showing prices, not recommending swarms or loops prematurely, strongly advising against big MCPs, killing features that have high usage but that aren't worth it anymore, and just generally staying away from any hype train we don't have a good gut feeling about. Pi and OpenCode are also particularly good and outspoken here. But if you have growth targets to hit, investors to pitch, and salespeople to keep happy, or if you didn't start this way from day 1, I can see it being tricky. At Amp, we're profitable, don't have salespeople, and have no sales/growth targets to hit, so we have it relatively easy. I often wonder what this tension is like inside other companies building agents. (And for the record: if you've shown me your Amp workflow and I haven't told you this directly, this post is not about you. :)




Anthropic is building OpenClaw faster than OpenAI is. OpenClaw proved a concept the entire industry had been theorizing about: your AI agent should live on your computer, not in someone else’s cloud, and you should be able to talk to it from anywhere. 318,000 GitHub stars. Then Steinberger joined OpenAI to build exactly this at scale. Here’s what OpenAI has shipped since: Codex, a desktop coding agent with no mobile remote control. ChatGPT Agent, which runs on a remote virtual computer in OpenAI’s cloud where it can’t see your local files. Developers are filing GitHub issues on the Codex repo right now requesting phone-to-desktop control. Third-party devs already built Taskdex and Remote Codetrol to hack around the gap with relay servers and Tailscale tunnels. Anthropic just shipped it natively. Dispatch: pair your phone with Claude Desktop, message Cowork from anywhere, come back to finished work. Cowork already had the VM running on your machine, full filesystem access, browser control, sub-agent coordination, and a skills system stored as markdown. Dispatch was the missing piece that turns the whole stack into something you can operate from your pocket. The reason this works when cloud agents can’t: Cowork reads your actual filesystem, your actual browser, your actual connected tools. When I ask it to cross-reference a local spreadsheet with a competitor’s pricing page, it can do that because both the spreadsheet and the browser are on my machine. A cloud agent would need me to upload the spreadsheet first, lose the file path context, and still wouldn’t have access to my connected Slack or Google Drive. The context is real because the machine is real. I’ve been running Cowork since launch. Five tasks dispatched every morning before my kids wake up: research briefs, competitor analysis, file organization, data pulls from local spreadsheets, editing passes on drafts. 90 minutes of active work compressed into 10 minutes of dispatching and 20 minutes of reviewing outputs. Dispatch changes what happens the rest of the day. An idea hits while I’m out, I message Cowork from my phone, the work is waiting when I get home. And the part that should keep OpenAI up at night: Anthropic didn’t need to acquire OpenClaw or hire Steinberger to ship this. They were already building the same architecture independently. Cowork launched in January with local VM execution, filesystem access, and markdown skills before OpenClaw was even mainstream. Steinberger validated the demand. Anthropic had already built the supply. OpenAI bought the architect. They’re still looking for the blueprints he left at Anthropic’s door.







