שָׁלִיחַ · shaliach · n. one you send to act in your name

Shaliach

Send one. A whole team goes.

It's 11 at night and you are still the one chasing receipts, answering "where's my order?" and typing the same details into five portals. Shaliach gives you emissaries: Claude Code agents on your own Mac or server, run by a chief of staff called Atlas. You text Atlas. Atlas hires the team, hands out the work, and checks with you before anything goes out the door.

The job description is two thousand years old

"A person's emissary is as the person himself."Mishnah, Berakhot 5:5

That is a lot of trust to hand to software. So ours carry your name, do the legwork, and still come back to ask before they sign anything.

What your emissaries actually do

You text one. It hires the rest.

Atlas, your chief of staff, hires the agents the job needs, briefs each one and folds their back-and-forth into one thread you can actually read.

Their own computers, not yours.

Every agent gets its own browser and terminal. Watch any screen live, and take the wheel whenever you like.

Nothing goes out without your nod.

Publishing, paying, logging in: it stops and asks on your phone. Allow once, always, or not today.

Tell them once.

Correct one agent and the whole team writes it down. "Never post before 7am" stays never.

They come back with the goods.

Videos, PDFs and screenshots land in the chat, not in a folder you will never open again.

On your turf.

Your Mac or your own server, your Claude plan. Shaliach never stores your Claude token.

What a shaliach is not

Send for one

1. Your server or your Mac

curl -fsSL https://shaliach.me/install | sh

2. The Mac app (macOS 14+, Apple silicon)

curl -fsSL https://raw.githubusercontent.com/yrks12/shaliach/main/scripts/install-mac.sh | bash

The installer says what it is about to do before it does it, and running it again upgrades: your token, sign-in and paired devices stay put. Prefer to read first? Here it is. Every agent is a real Claude Code session on your own Claude account.