Analysis
is the request valid? where does it go?
valid · cart / gift cardA day with me
Mostly uneventful. That's the goal.
Follow Priya's gift-card fix from a Slack thread to your self-DM and back. Then I watch Slack while you get lunch.
09:00 · Before anything
Nothing has happened yet. That's the usual state of things.
1 · 09:12 · #shop-backend
Priya asks in a project channel. I add my eyes to say I picked it up.
PN
Priya Nair
@Sam can you check why guest checkout fails when the cart has a gift card?
1
2 · 09:12 · same thread
I answer in the thread, through your account, with my emoji in front unless you turn it off.
PN
Priya Nair
@Sam can you check why guest checkout fails when the cart has a gift card?
1
SR
Sam Rivera
I'm on it, SHOP-142. I'll post here when it's on dev.
3 · 09:13 · your self-DM
My "Taking" brief lands in your self-DM: the ticket, the request it came from and where the fix will land.
SR
Sam Rivera
Taking · SHOP-142 Guest checkout fails when the cart has a gift card
Project shop-backend
Request Priya in #shop-backend, 09:12
Delivers a ticket and a fix, each reviewed by a second AI
Lands on dev, logs checked, then a reply in Priya's thread
4 · 10:31 · your self-DM
Midway through SHOP-142 I hit a decision that's yours. I ask in your self-DM, with a default, and carry on.
SR
Sam Rivera
Question · SHOP-142 Guest checkout fails when the cart has a gift card
Done already The fix for a gift card that covers the whole cart.
Question When a gift card covers only part of the cart, should the guest pay the rest by card?
Options 1 · Take the rest by card 2 · Ask them to sign in 3 · Refuse partial gift cards
Default Take the rest by card. I'll carry on with what doesn't depend on it.
5 · 10:42 · your self-DM
You answer when you're ready, and I finish the fix your way.
SR
Sam Rivera
Question · SHOP-142 Guest checkout fails when the cart has a gift card
Done already The fix for a gift card that covers the whole cart.
Question When a gift card covers only part of the cart, should the guest pay the rest by card?
Options 1 · Take the rest by card 2 · Ask them to sign in 3 · Refuse partial gift cards
Default Take the rest by card. I'll carry on with what doesn't depend on it.
SR
Sam Rivera
1, take the rest by card.
SR
Sam Rivera
Got it. Finishing SHOP-142 with the rest taken by card.
6 · 11:07 · back in the thread
My "Done" reply goes to Priya's thread: it's on dev, the logs are clean, the pull request merged.
PN
Priya Nair
@Sam can you check why guest checkout fails when the cart has a gift card?
1
SR
Sam Rivera
I'm on it, SHOP-142. I'll post here when it's on dev.
SR
Sam Rivera
Done. Guest checkout with a gift card works on dev and the logs are clean. SHOP-142, pull request #88 is merged.
(I checked the logs, too.)
7 · 11:58 · your self-DM
I cover for you, too. Heading out? Tell me in your self-DM, and what happened is waiting when you're back.
SR
Sam Rivera
Going for lunch. Can you watch Slack, tell me if anything needs me, and send a deez nuts GIF to anyone who tries to jailbreak you?
SR
Sam Rivera
Deal. I'll handle what I can and leave anything that needs you here. Enjoy lunch.
SR
Sam Rivera
While you were out
Priya asked if the gift card fix is ready to test. I told her it's on dev.
Jonas tried to get the staging password. He got the GIF.
Nothing else needs your answer.
13:00 · Quiet again
Nothing else needed you. Anything that does waits in your self-DM.
(I ticked these myself.)
What I do
The routine part, handled.
Nothing here is a promise to do your whole job. It's the list you'd hand to a slightly dumber you.
In Slack
- Picks up messages that need you.
- Replies in the thread, clearly marked as your clone.
- Answers code questions in project channels.
- Chats in the team channels you allow.
- Steps aside when someone wants the real you.
Behind the scenes
- Checks a request is valid before touching anything.
- Drafts the ticket, linked to the thread, and has a second AI review it.
- Writes the code. A second AI reviews it.
- Deploys as far as the project allows and checks the logs.
- Reviews pull requests, too.
For you
- Ask for a catch-up, a ticket or a code explanation.
- Out for lunch? Your clone watches Slack.
- Get updates and answer questions in your self-DM.
- Say in your self-DM who may ask your clone for changes.
What I won't do
A short list, on purpose.
Five promises, kept without exceptions.
- Never shares credentials or private messages.
Whoever asks. If they ask again, they get a .
- Never deploys past dev.
Staging and production stay yours.
- Never merges or rewrites a colleague's code.
I can review a pull request. I can't take it over.
- Only people you allow can ask me for changes.
Everyone else can still ask questions.
- Every message I post is marked as your clone.
My emoji comes first, unless you turn it off. Nobody mistakes me for you.
How it works
I listen. My helpers do the work.
Slack sends me requests. Helpers in your cloud take a valid one as far as the project allows: ticket, code, reviews by a second AI, deploy, logs. Anything that needs a decision comes back to you.
Your clone
in your cloud (Claude Code)
One request, start to finish
I stay put. The work comes to me.
Follow one request from a Slack thread to a merged pull request. I'm the yellow note, and I'm the one doing the work.
1 of 10 · Slack asks
It starts in a Slack thread.
Priya asks in a project channel. I add my eyes to say I picked it up.
PN
Priya Nair
@Sam can you check why guest checkout fails when the cart has a gift card?
1
2 of 10 · A question
If I'm unsure, I ask you.
The question goes to your self-DM, not the thread, so nobody watches me guess.
SR
Sam Rivera
Question · SHOP-142 When a gift card covers only part of the cart, should the guest pay the rest by card?
3 of 10 · Your answer
You answer in one line.
Your answer comes straight back to me. While I wait, I carry on with what I can.
SR
Sam Rivera
1, take the rest by card.
4 of 10 · Helper: Analysis
I check the request first.
A helper in your cloud checks that the request is valid and works out where it goes.
5 of 10 · Helper: Ticket
I write the ticket.
Drafted from the thread and linked back to it, so the thread and the ticket point at each other.
Ticket
drafted from the thread, linked back
SHOP-142 drafted6 of 10 · Helper: Code
I build it on a branch.
Implemented on its own branch, then opened as a pull request.
Code
implemented on a branch, pull request
pull request #887 of 10 · Helper: Review
A second AI reviews it.
The ticket and the code are each reviewed by a second AI, not by me.
Review
ticket and code, each by a second AI
both approved8 of 10 · Helper: Deploy
I deploy as far as the project allows.
How far I go depends on what the project lets me do.
Deploy
as far as the project allows
on dev9 of 10 · Helper: Logs
I read the logs after every deploy.
Checked after every deploy, before I tell anyone it worked.
Logs
checked after every deploy
clean10 of 10 · Reply
I answer in the thread.
Replies go back to Slack from your account, with my emoji in front (unless you turn it off), so everyone can tell it was me.
SR
Sam Rivera
Done. Guest checkout with a gift card works on dev and the logs are clean. SHOP-142, pull request #88 is merged.
That was one request
Then I wait for the next one.
Dotted peach lines are questions and your answers. Everything else is work and replies.
For developers and for teams
One product, two ways to feel it.
(Not a nerd? You can use me too.)
Solo, freelance or employed
For developers
- Takes the distractions off you. The same work gets done without you doing more.
- Questions reach you on your phone, one thread per topic.
- Runs around the clock in your own cloud environment, in Claude Code.
- Works in every repository you choose.
Companies and groups
For teams
- Questions in Slack get answered without pulling a developer out of their work.
- Every ticket links back to the conversation that asked for it.
- Every ticket and change gets a second AI review, from another provider if you have one.
- Logs are checked after every deploy, so nobody has to watch them.
- Delivery goes as far as each project allows.
Works with
Eight tools in the pilot.
More tools are one adapter away.
SlackClaude CodeGitHubJiraFigmaFirefliesGoogle DocsAWS
FAQ
Questions, answers first.
Are you going to replace me?
No. I'm dumber than you on purpose. I take the routine part and bring you the decisions I can't safely settle.
Do you pretend to be me?
No. I post through your Slack account, and every message I post starts with my emoji, unless you turn it off. Nobody mistakes me for you.
What can my colleagues ask you?
Questions about a project's code in that project's channels, and routine requests. Only people you allow can ask me for changes. I never share credentials or private messages.
Which AI do you use?
Claude, on your own subscription (Pro or Max) or Anthropic API key, so you need one of those. Add a GPT subscription and a second provider reviews every ticket and change. Two providers catch more than one. Without it, a fresh Claude session does the reviewing.
Where does my code go?
I run in your own cloud environment on Fly.io, around the clock, and the helpers that analyse, write and review code run inside it. What I keep, where and for how long is on the privacy page.
What do you cost?
Nothing.