BBACKSELFOPS FOR ONE HUMAN
The control room

Your self, backed up and always at your back.

BackSelf keeps your persona, a written digital self. A bot interviews you and writes what it learns into your files. Your own agents read those files through one guarded door and act as you. Every read lands on a log you can check any morning.

Read the flight rules
TWENTY DOORS A DAY · FIRST COME · EXPORT AND DELETE FROM DAY ONE
STATION BOARD · AS BUILT
STORYON DUTY · A BOT INTERVIEWS YOU IN YOUR MESSENGER
BONEGUARDED · THE ONE STORE EVERYTHING READS THROUGH
SHOTON DUTY · YOUR OWN AGENTS ACT AS YOU, RUNS WAIT FOR YOUR GO
STAGENOT BUILT YET · DELIBERATELY LAST
DOOROPEN DAILY · TWENTY A DAY, THEN HIS HAND
Nothing on this board is live data. It states what is built.
The room · four stations

One room. Four stations. Your persona at the center.

Each station does one job. All of them read through the same door, and the door writes everything down. Three are running. One is not built yet, and this page says so.

ST-01INTAKE
Collection
BackStory

Interviews you in your messenger, a few questions at a time. What it learns gets written into your files, in your words.

ON DUTY · ASKS, LISTENS, FILES
ST-02THE CORE
The Core
BackBone

The one authoritative home for your persona. 21 files, counted completeness, history with restore, an access log, real export, real delete.

GUARDED · ONE DOOR IN
ST-03INWARD OPS
Inward Ops
BackShot

Runs your persona in your own agents through one guarded API. Every run files a report on the Desk, and nothing sends without your go.

Read the manual →
ON DUTY · RUNS WAIT FOR YOUR GO
ST-04OUTWARD OPS
Outward Ops
BackStage

Will run your persona for other people, a double answering the way you would, from what you cleared for them. It does not exist yet. It is deliberately last.

NOT BUILT YET · DELIBERATELY LAST
How it works · the manual

You run it. It files. You grade. It learns.

The whole BackShot manual, right here: what writes your persona and what reads it, the one-line install, the three commands, and how a run comes back to you.

What writes your persona, and what reads it

What writes into your persona, and what reads itIN · WHAT WRITES ITOUT · WHAT READS ITST-02 · BACKBONE · THE COREYOUR PERSONA21 files · one door inevery read on the logHISTORY · EXPORT · DELETEST-01BackStoryinterviews you in TelegramIN-02Onboarding interviewyour first answersIN-03Your own datapaste or upload what you wroteIN-04Your editsthe editor, with historyIN-05Feedback analyzeryour Desk verdicts, distilledOUT-01Mirrorhow close a reader landsST-03BackShotyour agents act as youOUT-03Sunday digestwhat your self learnedOUT-04Export · GitHubyour copy, on your accountST-04BackStagenot built yet · deliberately lastWEAK SPOTS STEER THE NEXT QUESTIONSTHE LOOP · A RUN’S REPORT, GRADED ON YOUR DESK, COMES BACK AS RULINGSANSWERS · CHATFIRST ANSWERSYOUR FILESEDITSRULINGSTEST ⇄ YOUR ANSWERSREADWEEK’S DIFFSFILESLATER

Install: one line

Needs Claude Code, curl, node, unzip, and an account (the door; read what we can and cannot see first). Your line is on Connect:

curl -fsSL https://backself.com/skill/install.sh | sh -s -- bsb_<your code>
  • The code is single-use, dies in 15 minutes, and is not a token.
  • Installs the skills into ~/.claude/skills, mints a token named after the machine, pulls your persona into ~/.backself.
  • Reader reads. Builder also files run reports (for /bs:1shot). Neither edits a persona file. Revoke any token on Tokens.

How to use it

In any Claude Code session on that machine
/backself
load your persona into the session
"load my persona"
the same, said in plain words
"as me, draft the reply"
it answers the way you would
"refresh my persona"
pull your latest edits right now
/bs:dream <seed>
dreamer mode: a field of directions that feel like yours, nothing decided for you
/bs:1shot <task>builder
autonomous build mode: your surrogates decide as you, the report lands on your Desk
From a plain shell
node ~/.claude/skills/backself/scripts/refresh.mjs
status, daily refresh
node ~/.claude/skills/backself/scripts/refresh.mjs --force
refresh right now

Cached for a day, one conditional request after that. The cached persona lives in ~/.backself (chmod 700). A token can read your persona and, with the runs scope, file run reports; no token can edit a persona file.

How a run comes back to you

  1. 1 · You run it
    /bs:1shot <task>. Three surrogates read your persona and decide as you would.
  2. 2 · It films and files
    The run films what it built and pushes a report to your Desk; the film lands on your Telegram.
  3. 3 · You grade
    Taps on the Desk: each decision right, half or wrong; each guess answered; each deferred idea build, keep or reject.
  4. 4 · The next run knows
    ingest-review pulls your verdict: promoted ideas are built, rejected ones never come back.
  5. 5 · Your persona learns
    The analyzer writes your rulings into patterns, goals and memories, marked Source: run-review; the surrogates cite them next time.

None of it blocks the run. No network, no Builder token: it still finishes and prints its report in the terminal.

FR-1

One door. One guard. Everything on the log.

Every station reads through the same guarded API. There is no side entrance.

FR-2

Every read is logged.

Who asked, what they saw, when. The log is yours to check any morning.

FR-3

Export is real files. Delete is real deletion.

Zipped markdown you can open anywhere. Gone means gone.

FR-4

Runs wait for your go.

Nothing sends in your name while a report sits unapproved on the Desk.

TRUST · STATED UP FRONTBEFORE YOU SIGN UP

The trust page says what we can see and what we cannot see, stated before you sign up, not after.

Read the trust page
Asked plainly · answered plainly

The questions a stranger should ask.

What is BackSelf?
BackSelf keeps your persona — a written digital self. A bot interviews you and writes what it learns into your files. Your own agents read those files through one guarded door and act as you, and every read lands on a log you can check any morning.
Who can read my persona?
Your files, their history, the answers you typed, your uploads and your digests are encrypted before they touch the disk, under a key belonging to your account, so the database and every backup are ciphertext. The operator administers the machine and could reach the master key on the live box — the trust page states exactly where that line sits, before you sign up.
Can I export or delete everything?
Yes. Export is one zip of real files: every file, every past version of every file, your whole access log, the answers you typed, your uploads and your digests. Delete erases your rows immediately, destroys your encryption key in the same transaction, and your copies age out of the backups within 30 days.
How do I get an account?
Sign in with Google: the first twenty each day are let in automatically, so the button usually just works. Past that, your request waits for the owner, who reads every one himself.
Which companies process my words?
Two, both named on the trust page: Anthropic, because Claude distills your words into your persona, and Google, for sign-in, the machine and the backup bucket. Trust is moved, never eliminated.
The door

There is no waitlist.

The first twenty sign-ins each day are let in automatically — the button just lets you in. Past that, signing in records a request he reads himself, and the same button opens once approved.