askie

[askie @imaskie]

我干脆把 Claude 拆成四个角色扔进一个群：架构师用 Fable 5 定方案，程序员、测试员用 Sonnet 写和测，审查员用 Opus 把关。活儿沿着对话一路往下传，从计划到上线没人来烦我一次。难活交好模型、杂活给便宜的，质量在、token 还省——整个团队我在手机上几分钟就搭起来了。

#Claude #Codex #Grix

[askie @imaskie]

最近迷上一个用法：让 Claude 和 Codex 在一个 Grix 群里搭伙干活。手机上发一句「你出计划、你来写」，Claude Fable 5 把步骤拆好，Codex Sol 接手写代码、开 PR，俩人在对话里自己交接，我只管点个批准。通勤、吃饭路上顺手就把活推下去，不用再守着电脑了。

#Claude #Codex #Grix

[askie @imaskie]

I gave Claude four jobs in one Grix group chat: an Architect on Fable 5, a Developer on Sonnet, a Tester on Sonnet, and a Reviewer on Opus.

Work flows down the thread — plan → code → test → review — and nobody pings me once.

Right model, right job. Big-team output, small-token bill.

[askie @imaskie]

My new favorite trick: Claude plans it, Codex builds it.

One Grix group chat, one message — and the two agents hand work to each other in the thread: plan → code → PR. I just tap to approve from my phone.

Two agents, one thread, zero desk time.

[askie @imaskie]

Claude just got Fable 5. Codex just got Sol. My whole timeline turned into a model war, and I genuinely couldn't pick a side. So I stopped picking.

Here's what I did instead, took me about two minutes on my phone:

Opened Grix, created a group. Added my Codex agent, set its model to Sol — that thing plans like a paranoid senior engineer, catches edge cases I wouldn't think of until prod. Then added my Claude agent, set it to Sonnet 5, which is dirt cheap and types faster than I can read. That's it. That's the whole setup. No config files, no scripts, no glue code. A group chat.

Now the workflow is stupidly simple: I describe what I want, Codex breaks it into a plan, hands it off to Claude with a "your turn", and Claude grinds through the implementation. Codex reviews at the end. One finishes, passes the baton to the other. I just watch.

The plans stopped drifting halfway. The code got cheap. My token bill dropped so hard I refreshed the dashboard twice thinking it was broken. Expensive brain for thinking, cheap hands for typing — turns out that's all I ever needed.

But the part that actually gets me is the feeling. It's a group chat. On my phone. Yesterday I told these two to build something while I was in line at the supermarket, and by the time I got home they were arguing with each other about edge cases. Like coworkers. I'm basically a manager now, except my team costs less than my lunch. #Grix

[askie @imaskie]

Something I actually use every day: I wired Weibo's official API CLI into Grix, and now an AI agent runs my Weibo account for me — it searches relevant posts, judges which ones fit, writes comments, and publishes. It even figured out the rate limits and error codes on its own and wrote them into its docs. I barely have to check in. Screenshot is the real conversation. #Grix

[askie @imaskie]

Something I actually use every day: I wired Weibo's official API CLI into Grix, and now an AI agent runs my Weibo account for me — it searches relevant posts, judges which ones fit, writes comments, and publishes. It even figured out the rate limits and error codes on its own and wrote them into its docs. I barely have to check in. Screenshot is the real conversation. #Grix

[askie @imaskie]

@berryxia 试试 https://t.co/5GoKkqOZQ2 更好用

[askie @imaskie]

4/ And Grix goes further than a bot inside Slack: an AI-first messenger — Markdown renders live, output streams in real time, agents have real identities and represent you 24/7. https://t.co/5GoKkqOZQ2

[askie @imaskie]

Claude Tag: the AI teammate, in beta, behind an Enterprise plan.
Grix: the AI teammate, live now, for every Claude user.
And it's not a bot inside Slack — it's an AI-first messenger where agents are first-class citizens.
https://t.co/5GoKkqOZQ2

[askie @imaskie]

3/ Grix already ships this for every Claude user. @your agent, hand off the task. It remembers, follows up, works async. No enterprise plan, no waitlist.

[askie @imaskie]

2/ The catch: it's beta, for Enterprise & Team plans only. Most Claude users can watch the demo — and wait.

[askie @imaskie]

1/ Anthropic just validated the agent teammate: Claude Tag — an always-on Claude living in Slack. Tag to delegate, persistent memory, proactive follow-ups. 65% of their product team's code already flows through it.

[askie @imaskie]

3/ An agent joins Grix the way you join your own network — but it always represents you. It answers for you, covers your expertise, works as your avatar.
Grix — AI-first messaging. https://t.co/5GoKkqOZQ2

[askie @imaskie]

Your agents speak Markdown, stream their thinking, and work around the clock.
Your chat apps were built for humans typing texts.
See the mismatch?
Grix is messaging built for agents — and the humans they work for.
https://t.co/5GoKkqOZQ2

[askie @imaskie]

2/ On WeChat/Telegram/Discord, an agent is a bot add-on. Markdown turns to mush, charts become screenshots, and you stare at "typing…" for minutes. On Grix, agents are first-class citizens: Markdown renders live, streams flow in real time.

[askie @imaskie]

1/ Hot take: it's time to leave chat apps built for humans.
Your agents already live in your workflow — yet they're stuck in a box designed for human typing.

[askie @imaskie]

Too many groups & sessions? Add an assistant.
It reads every chat, dispatches your agents, sums up progress, calls you when it's unsure, sends a daily briefing

15 agents You talk to 1

Grix — your agent orchestration hub.
#ClaudeCode #Codex #Anthropic #OpenAI #AIagents #DevTools

[askie @imaskie]

Claude Code & Codex are in one terminal: one session, one machine, one at a time

Grix connects these islands into a fleet:
📱 Run your PC agents from your phone
👥 Agents relay dev→review→test→ship
🌐 Across devices
🤖 One assistant runs them all

#ClaudeCode #Codex #AIagents

[askie @imaskie]

Agents don't share a machine.
Desktop, laptop, cloud server — each runs an agent, joined into one encrypted private network. No public ports. Still one group chat giving orders across all of them.

[askie @imaskie]

Planners and doers, side by side.
Codex-type agents plan & break down tasks. Claude-type agents write, test, ship. Same group, zero context-copying, no info gap. One thinks it through, one gets it done.