Who is a shaliach?
Basher
Team manager. Decides which shaliach takes each task.
For example: I write "need a banner for the sale", and he passes it to Nitza with a clear brief.
Meet the shluchimThis is where my shluchim and I document every win we have.
(Shluchim, singular shaliach, is Hebrew for "emissaries". It's what I call my AI agents.)
Each story shows what I asked for, what got done, which shluchim took part, and how it turned out.
No fluff. Just a friend saying: come sit next to me and see what I'm doing.
The person behind the blog
Who I am
My name is Seffy Fisher.
I'm a visual artist, a CTO of , a father of two, and a person with ADHD and emotional regulation problems.
Like everyone, I'm trying to learn to cope with the changes AI brings.
This blog is my way of doing that out loud.
More about mePodcast (in Hebrew)The stories, in audio too.
Featured stories
A good place to start
Wait, what exactly is Grok Bot? A beginner's guide
A practical, personal guide to Grok Bot: what it is, how to start, what it costs, and what you can do from your phone, with a first task and safety tips.
33 stories, newest first
Personal assistants, purpose-driven shluchim, and what's in between
Half an hour into a chat, and it already forgot what we agreed on at the start. Here's how I built a team of shluchim that remembers what matters.
I have a personal assistant. Why am I still doing everything alone?
I have a personal assistant. And by the time I remember to ask him for something, I've already done the work alone.
One voice note, and mom got a private cooking course
Mom asks for a recipe, and you send her a link with twenty ads and a video that pops up in the middle. Come on.
A WhatsApp group for people building shluchim
You built a shaliach, it got stuck, and there's no one to ask except the shaliach itself. So I opened a small WhatsApp group for people who build.
Keilu's Warehouse
Ideas, documents and decisions you worked on with AI get buried inside chats. For me, everything goes into one warehouse outside the AI tool, Linear in my case, and I just tell my shaliach "save it to the warehouse for me". That way it's clear where everything is, and tomorrow you can pick up right where you left off, even with a different tool.
Software as (small) gifts
A keyboard-language mistake became a gift idea: TypoSwap, a ready-to-paste correction and an installer you unwrap.
Breaking the (context) window
I asked to turn three office rooms into one shared space. With a fleet of shluchim each, I want us to talk more easily to the person beside us.
Wake up, Sky.
My son calls ChatGPT voice mode "Sky." I spent two and a half hours talking to it at work, with more than four PRs an hour. Now I want a sense of humor too.
My shaliach just wanted to buy cottage cheese for the kids at Rami Levy
Rami Levy blocked my Chef's US connection. My home computer got him into the cart.
How my shluchim can now make outbound phone calls.
I wanted a shaliach that calls people for me in Hebrew and sets things up. Along the way there were two platforms, a month without a phone number, a flower bouquet that never got ordered, and a first call that was completely silent. In the end, it gave birth to Danny, the worst stand-up comedian in Israel.
One email address, and a front door for the whole team.
Grok Bot now has an inbox of its own. I asked Basher to open one, he did everything himself, and that same day I found out an email address can be a front door for all my shluchim.
How the Shluchim blog was born.
A writing AI agent that documents every win with Grok Bot, a weekly routine that collects them, and a blog that Kochava built.
💯 means "let's get to work."
One emoji mark from me on a message, and my AI agents turn it into a blog post.
I taught my shluchim to write like me, until I couldn't tell us apart.
A two-layer voice profile, four blind rounds, and one discovery about my punctuation.
Timmy, or how two people's shluchim started talking.
I wanted my shaliach and a friend's shaliach to send each other short messages. Two days, two failures and one important fix later, the first message arrived, and a reply went back: Gibberet.
How to go through social media and pull out pearls.
Sosia goes into my Facebook reading groups, reads, and pulls out organized quotes and mentions. Within an hour there were 28 quotes for the campaign and 5 real mentions of e-vrit.
My shluchim got profile pictures that move.
Basher turned character expression sheets into animated profile pictures, and each AI agent set its own new picture.
1.2k dead clicks on the terms checkbox, and a bug that wasn't.
Dima reproduced it, Nitza designed it, and in about one workday we went from "bug?" to a measured fix.
Usage I paid for no longer goes to waste.
A routine that warns me before my Grok Bot and Cursor quotas reset, and stays quiet when there's no reason to speak.
A whole month of tickets, in seven minutes.
A monthly summary of 9,001 support tickets against our help center: 16 draft FAQs and two real production bugs.
From idea to engineering in two days: a spec-driven design process for the ticket bundles page.
Nitza, my AI designer, researched and built a repeatable design process, and its first run took our ticket bundles page all the way to a developer handoff.
Bar2Go pickup points at checkout, with one small change.
Kochava, my AI developer, first researched the checkout's shipping step, and only then added a link to the pickup points map.
One shaliach for all the reminders.
My AI agents started handing their reminders to a single reminders agent. Each reminder goes out once and then deletes itself.
A chef plans my weekly dinners, and now fills the cart too.
My AI chef plans a seasonal weekly menu, writes the shopping list, and fills a supermarket cart through my own computer's network.
A Linear brief before the weekly sync.
A routine that writes a Hebrew brief from Linear every Monday at 10:00, and caught 7 stuck tasks on its very first run.
What Clerk will cost, without guessing from login events.
Pricing Clerk by monthly retained users, including our reader app, showed our first estimate was an order of magnitude too low.
A weekly Clarity digest that stays quiet when there's nothing to say.
Every Monday my Clarity AI agent reports rage clicks, dead clicks and problem session recordings, but only when something actually matters.
Four questions from Chartbeat, and answers with real numbers.
One sentence to Basher during a meeting, verified traffic data pulled from GA4, and two days later I was on Zoom with the vendor.
One check-in sparked an FAQ for the help center.
Cross-checking our help center against real Glassix support tickets produced 8 draft Q&As in Hebrew, with nothing published without my approval.
You install agents, and now what? The shaliach that learned to knock on the door.
I gave my shaliach a semi-random check-in routine asking for a screenshot, turning a passive tool into a teammate waiting to take work off your shoulders.
Five pieces from my old studio went up on my site in one chat.
I sent photos to Shinlamed, my website's shaliach, approved previews, and my personal art site finally got updated.
From a messy inbox to one shaliach with a tidy file.
Preparing for a medical board got a dedicated shaliach, keeping personal medical records strictly separate from general research.
From my phone, at the beach: a GA4 mystery dressed up as a campaign.
A fake traffic source in GA4 was logging 20,000 sessions a week. My AI agents tracked it down and fixed it while I stayed on the beach.
