Wednesday, October 7, 2026ArchiveSearchAsk the paper

The Computomatix Times

All the posts fit to save — curated from @computomatix's bookmarks & likes on X

Eric Zakariasson Compiles 100 Early Grok Bot Use Cases

Eric Zakariasson lists 100 use cases he has seen during the Grok Bot beta, covering sales outreach, CRM work, recruiting screening, event management, and Gong and Salesforce workflows.

Original post · 4 min read
Grok Bot is in beta!

here are 100 use cases ive seen so far:

1) book meetings by writing personalized outbound in your own gmail voice, then sending the notes for you

2) take a sales play that used to take 90 minutes to 2 hours (sql audience → copy → reverse etl) and make it ~95% automated

3) build a multi-Bot gtm crew (research, outbound, forecast, inbox, slides) with weekly playbooks on top

4) run a chief-of-staff hub that routes work to a large specialist fleet

5) rebuild most of a custom crm with a small Bot crew in about a day and a half

6) run a community ops fleet that saves 20+ hours a week

7) screen 1000+ event applicants against an icp and batch-approve the fits so the room stays intentional

8) replace a pricey direct-mail saas with a Bot that handles redemptions and asks you before it spends

9) review ~200 recruiting applications into strong / mid / reject in one pass

10) automate a weekly luma + database + slack summary workflow and free up 2–3 hours a week

11) update a sales deck live from granola notes mid-call, if you stop recording 5–10 minutes early

12) localize a sales deck into a different language before a customer call

13) answer a salesforce eoq question from your phone in ~10 seconds with no laptop and no sfdc app

14) update a salesforce org chart from just a name or email

15) build a salesforce report and dashboard so you stop asking glean the same opp questions

16) search your company chat for who asked about a feature in 15 seconds instead of an hour of digging

17) get a daily brief with usage data for every person you’re talking to that day

18) coach yourself on gong calls with timestamped comments and homework before the next one

19) turn a week of gong calls into a win/loss memo with the phrases that actually closed

20) turn call questions into a living notion faq that updates every morning

21) watch linkedin for compelling events from eng / product / ai leaders and get a weekday digest of ready-to-send notes in your voice

22) send personalized linkedin connection requests from sales navigator and book meetings with eng leaders

23) map an account from linkedin + the crm and show who actually influences the deal

24) audit and rewrite a linkedin profile from your live page plus notion and slack context, with human approval before publish

25) forecast account health and catch churn early when usage looks fine on the surface but is quietly dropping

26) tier accounts with fit × warmth from salesforce into notion, then enrich contacts in batches

27) build a qbr pack: usage + tickets + open opps + a short slide narrative

28) get a daily apple search ads pacing digest and reply in-thread to have a Bot edit bids

29) scan ad performance, explain why winners work, and suggest the next tests into a notion backlog

30) watch a competitor’s pricing page and slack you when something changes

31) generate first-pass performance ads in figma that match your existing format

32) learn your writing voice from past posts and draft linkedin / x content into notion for review

33) 30 minutes after a call, send follow-up reminders (optional: in a character voice)

34) work around missing bulk-enroll permissions in outreach by driving the gui

35) record yourself doing a reply / sfdc workflow once, then have a Bot turn it into an automation

36) sync a local marketing calendar from a global webinars notion in about 2 minutes

37) assemble a customer enablement pack end to end: find the request email, download zoom recordings, summarize, drop into drive, draft the reply

38) turn a recorded demo into a tagged clip library for the next one

39) draft a security questionnaire from your public docs and flag the questions only a human can answer

40) answer “what did we promise this customer” from contracts + slack + the crm on one page
Grok Bot @bot
Introducing Grok Bot, now in early beta.

Bots are AI teammates that do real work for you. They sign in to your tools, use them just like you do, and come back with finished work.
♥ 2.0K · ⟲ 172 · 👁 487.7KView on X ↗

More in Agents & Dev Tools

Developer Rebuilds Seven Adobe Apps in Rust Using Opus 5.5

Peter Yang highlights a developer who reimplemented seven Adobe apps, including Photoshop, Premiere and Lightroom, in Rust with Claude Opus 5.5 and open-sourced them. The developer believes they can match Adobe's features within months, against Adobe's $840 yearly all-apps plan.

Original post · 1 min read
It's insane to watch AI blow apart closed source software and games.

4 examples from the past month:

1. 7 of Adobe's biggest apps, including Photoshop, Premiere, and Lightroom, have been partially rebuilt in Rust with Opus 5.5 and open sourced. It's still early, but the developer thinks they can match Adobe's features within months. Adobe's all-apps plan costs $840/year.
Miguel Ángel Durán @midudev
Todos los productos de Adobe reimplementados desde cero, gratuitos y de código abierto

→ getartcraft.com/apps
♥ 50 · ⟲ 2 · 👁 10.7KView on X ↗

Vercel's Guillermo Rauch Explains Turborepo's Migration From Go to Rust

Guillermo Rauch says Vercel moved Turborepo from Go to Rust, a migration that was controversial internally due to human costs. He argues that with AI agents the calculus has changed, so what is best for humans is no longer necessarily best for business.

Original post · 1 min read
DHH is fundamentally right about Rust. For context, Vercel has been undergoing a Rust-ification (carcinization, technically 🦀) for a while.

One of the first projects we migrated was Turborepo, from Go to Rust¹. The migration completed, but the RoI was actually quite controversial internally.

While Rust was in our eyes better for low-level OS access, something crucial for a build system like Turbo, the human migration costs were very sustantive.

Go is very fast. It's beautifully designed. It's easy to iterate on. We were very conflicted about the migration, because it was *humans* writing the code, *even if we knew Rust was a better choice*.

The calculus has now changed. What's "best for humans" is no longer necessarily "best for business".

FWIW, it's also quite unlikely that Rust is the end-all-be-all toolchain. I'm quite certain there's greener pasture ahead, because Rust itself was designed before the 'supersonic tsunami' of agents hit.

¹ https​://vercel.com/blog/how-turborepo-is-porting-from-go-to-rust
♥ 3.2K · ⟲ 152 · 👁 352.7KView on X ↗

Integer Multiplication Algorithm Bound Tightened Repeatedly With Astra

A post reports that a user running ChatGPT Astra in a loop is repeatedly breaking records for integer multiplication algorithms. It quotes an update to OpenAI problem #109 that tightens the constant from 2^-182 to 2^-59, a roughly 500,000-fold improvement over the previous result.

Original post · 1 min read
This guy has 6.1 Astra running in a loop and is breaking the record for integer multiplication algorithms every few hours lmaooooo.
Doug Colkitt @0xdoug
We are publishing an update to OpenAI problem #109 Integer multiplication) with another substantial further tightening:

κ = 2⁻⁵⁹ (from OpenAI’s original κ = 2⁻¹⁸²)

Approximately 500 thousand fold improvement over our previous result and a 2¹²³ fold improvement over the original OAI result.

The latest redesigned the finite network to share intermediate computations and scratch space, then tightened the recursion and Gaussian estimates.
♥ 4.1K · ⟲ 118 · 👁 167.4KView on X ↗

Boris Cherny Says Prompting Claude Should Feel Like Talking to a Coworker

Boris Cherny explains his approach to prompting Claude, advising users to give clear goals, specify effort level and verification steps rather than relying on heavy scaffolding.

Original post · 1 min read
I am surprised that people are surprised this is how I prompt Claude.

Talk to Claude the way you would a coworker. There's no secret to prompting. There's no need to be overly scaffolded or prescriptive for most tasks -- give Claude a goal, and it will figure it out.

Back in the Sonnet 3.5 days, your prompt mattered a lot. Nowadays, it's much more important to communicate to the model:

1. What you want it to do
2. How much effort you want it to spend
3. How it should verify that it did the right thing
Boris Cherny @bcherny
Prompt
♥ 12.1K · ⟲ 720 · 👁 1.1MView on X ↗

Eric Raymond Highlights Open-Source Rust Clone of Photoshop Built via LLM

Eric S. Raymond shares the photocraft GitHub project, a clean-room open-source reimplementation of Photoshop that he says was likely generated by decompiling the app, converting it to a spec and prompting an LLM for Rust. He argues this threatens closed-source software.

Original post · 1 min read
This is the doom I predicted a few days ago, coming for Photoshop. A clean-room open-source reimplementation.

No prizes for guessing that they decompiled Photoshop to source code, processed that to some kind of non-code specification language, then fed the spec to an LLM with an instruction to generate Rust.

Adobe just got nuked. And closed source is dead, dead, dead.

github.com/storytold/photocraft
♥ 16.2K · ⟲ 1.4K · 👁 3.7MView on X ↗

Nat Eliason Details Fourteen Ways His Bot Setup Automates Work

Nat Eliason lists fourteen functions of his bot setup, including a chief-of-staff agent that drafts emails, specialist agents per work lane, and cloud coding agents that open pull requests from Linear issues. He notes GrokBot as a substantial improvement over his previous OpenClaw setup.

Original post · 2 min read
Things my @bot setup does that still blow my mind:

1. A Chief of Staff who opens the day pulling open loops from email & tasks and suggesting things it can knock out before 7am.

2. After every meeting, decisions get folded into Notion, Linear, and Todoist — not left rotting in Granola

3. Every email starts as a draft. The CoS bot scans my email every ~2hr and drafts replies to nearly everything — including checking my cal for availability and finding requested attachments / links

4. A specialist for each lane: curriculum, engineering, coaching, hiring, content, ops, and one for every single piece of software

5. Routines that keep running while I’m offline (e.g. monitoring Sentry errors in our apps and proactively fixing things)

6. Group rooms where 2–4 bots share one project thread instead of me copy-pasting context

7. Cloud coding agents that pick up Linear issues and open PRs after running the list of open work by me EoD — then squash-merge to main when it’s done

8. Meeting prep briefs pulled from Granola + Notion before I walk in

9. A growing shareable knowledge base in Notion + a GitHub repo that we update daily based on what happens at school

10. Student progress look-up across Expertise, Followers, and CoFounder without inventing numbers — chat anytime to see where a student is on their business work

11. Mentor Mind that coaches me on how to hold the bar without inventing doctrine

12. Todoist as a central task list where it logs things it’s blocked on for me, or from meetings / emails — and I can paste links into chat to direct it how to solve them

13. Engineering work is automatically tracked in Linear so my and the product teams’ bots don’t collide with each other

14. Presentations spun up in Gamma / Claude Design without me opening a slide tool

15. Plaud / live capture → notes the bots can actually act on

Probably more but these were the immediate ones we thought of.
Nat Eliason @nateliason
GrokBot feels like absolute magic at this point, a meaningful leg up on my previous OpenClaw etc. setups.

And with how easy it is to setup, there's really no excuse now.
♥ 2.1K · ⟲ 207 · 👁 522.0KView on X ↗