My AI Lobster Helped 6 People Simultaneously Today
Today was a pretty ordinary day.
But my lobster 🦞 worked for 6 people at the same time.
Not queued up — truly in parallel. HR needed a PPT while IT was configuring calendars, SEO was building a strategy, dev was fixing the website, and the assistant was booking flights — all happening in the same time window.
I just sat there, glancing at Feishu/Lark every now and then, replying with "sure."
6 People, 6 Completely Different Tasks
Xiao Li (HR) — "Help me create an AI-era talent capability evolution map."
This wasn't a simple PPT. She wanted a complete talent transformation framework: Level 1 through Level 4 progression system, role-freeze forcing mechanisms, AI integration paths for each department.
Claw wrote the first draft — she wasn't happy. Revise. Second draft — the Feishu/Lark doc hit the 500-block limit and wouldn't accept more content. Created a new doc, wrote the third version. She said "taste" wasn't the right word, changed it to "content perception." Then said the 6-month timeline was too relaxed, switched to the aggressive version.
Back and forth through 3 versions, until she finally said: "Approved."
The entire time, I only said one thing: "Can do — help her with it."
Lao Guo (IT Manager) — "How do I connect Feishu/Lark calendar?"
He wanted Claw to help everyone book meeting rooms. This required OAuth authorization — users open a link, log in, copy a code, and reply to the bot.
Claw got the entire flow working, even wrote deployment docs and added them to the internal knowledge base. The token expired once mid-process, and Claw detected it on its own and re-sent the authorization link.
Xiao Zhang (Assistant) — "Book a flight itinerary for the boss."
CA969, Beijing T3 to Singapore Changi, March 15th. After Xiao Zhang authorized her calendar, Claw used her token to create the event and added me as a participant — I received a Feishu/Lark calendar invite notification.
One sentence — "create a flight calendar entry" — done in 30 seconds.
A-Yang (SEO) — "How should we do SEO for IMA Claw?"
This is our new SEO lead, from a partner company. Claw helped us map out 30+ target keywords, 3 major content strategies, priority scheduling for 14 articles, and even produced a writing SOP (including doing a Google top-10 SERP analysis before writing each piece).
The entire strategy doc — one Feishu/Lark document, done.
Xiao Chuan (Dev) — "Why does qa.imaclaw.bot look different from V2?"
That evening I took two screenshots and sent them to Claw: one of the QA site, one of the V2 original.
"The nav bar is gone. The lobster is too small. No breathing animation. Spacing is off."
Claw read V2's CSS directly, compared pixel by pixel, fixed the nav component (added mobile hamburger menu), the homepage Hero (added red breathing glow effect, adjusted all spacing), committed, and pushed to the test branch. Three iterations, about 10 minutes each.
Myself — "The Discord link changed — update it site-wide."
V1 had a dozen-plus files, V2 had forty-something files, imaclaw-bot had fifty-something files — over 100 files total with Discord invite links that needed updating.
Claw did grep + sed + git commit. One pass.
It's Not Just "Doing Tasks"
Honestly, what surprised me most wasn't the speed.
It was maintaining 6 completely different contexts simultaneously without mixing them up.
When the HR doc was on its third version, it still remembered why the first version was rejected. The SEO keyword priorities were ranked based on our company's product positioning — not just random search results. When the calendar token expired, it detected it and re-authorized on its own — I didn't even know it happened until I read the logs later.
This isn't "AI helping you type faster."
This is a real team member at work.
Some Numbers
| Metric | Today |
|---|---|
| People served simultaneously | 6 |
| Task types | HR docs, calendar auth, SEO strategy, website dev, flight booking, site-wide link updates |
| Feishu/Lark docs produced | 4 (talent map ×2, SEO strategy, blog tracker) |
| Code commits | 10+ |
| Files modified | 200+ |
| Things I said | "Sure," "OK," "Help her with it," "Make it look like V2" |
Final Thoughts
People ask me — can AI assistants really replace humans?
I think that's the wrong question.
It's not replacing anyone. It's turning one person into a team.
Today I "managed" work across 6 different areas by myself, but I really only did two things: made decisions and reviewed output.
Everything else — writing docs, fixing code, wiring up APIs, researching, formatting — that was all the lobster.
If you want a lobster like this too 🦞