ST-03 · Inward ops · the manual

BackShot: your persona in your own Claude Code

Your persona, read by your own agents. The drawing is the whole story; the rest is the manual.

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.