Tyre Swing OS · Onboarding
Your first day, top to bottom. About 30 minutes. A few steps need Matt (he can do his from his phone). By the end, you can run and build the Tyre Swing agents from your own laptop.
Tyre Swing's back office is run by around 24 small AI agents: the daily dashboards, freight quotes on every order, spam-folder rescue, bank-payment matching, ads, product hygiene, SEO tracking, and more. Each does one job on a schedule so a person doesn't have to.
They live in one GitHub repo (the code) and run in the cloud on Railway (the schedule), project tyreswing-os. Matt's personal agents live somewhere else entirely (matthew-os) — you never touch or see that world.
Your daily health screen is the Tyre Swing OS Control Tower sheet → Dashboard tab. Green = fine.
Gets you into the code.
github.com → matthew2rs/tyreswing-os → Settings → Collaborators → Add people → jackie@tyreswing.com.au.
Open the invite email → Continue with Google → sign in with jackie@tyreswing.com.au. That one click creates your GitHub account and accepts the invite.
This is where you'll do everything.
claude.com/claude-code → download the Windows installer and run it. (You're on a PC, so grab the Windows version.)
Easiest way: open Claude Code and tell it: "clone https://github.com/matthew2rs/tyreswing-os.git and open it." It handles the download and the GitHub sign-in for you.
Prefer to do it yourself? Open PowerShell (search it in the Start menu) and run git clone https://github.com/matthew2rs/tyreswing-os.git. You don't need to memorise where it lands — Claude Code knows.
The folder is the context. Claude reads the repo and knows the whole system. Ask it anything — "what agents run on Mondays?", "why did spam rescue flag this?" — it knows.
Lets your Claude reach the cloud — Tyre Swing only, never Matt's.
Railway → tyreswing-os project → Settings → Tokens → create a project token (production) → hand it to Jackie privately (not email or chat).
Tell your Claude "set up my Railway token" and paste it when asked. It stores it safely on your PC and wires up the tooling. You never touch a setting by hand. (You don't get a Railway login — Matt manages that; the token is all you need.)
Read only — nothing to do today.
CREDENTIALS.md (10 min)It's the map of every key the agents use, whose login each is under today (mostly Matt's), and the exact steps to move each one to your login when it breaks. Rule of thumb: each time a key fails, that's the moment you make it yours — your Claude walks you through it. Change nothing now.
Three moves. That's the whole job.
Control Tower → Dashboard tab. A red row? Open the Run Log for that agent, or just ask your Claude "why did X error?"
Describe what you want to Claude in the folder. It edits, you review, it commits and pushes — and pushing auto-deploys. Nothing manual.
"Build me an agent that does X every Monday." Claude follows the recipe in the repo. Same as changing one, just new.
Two things to build confidence.
Tell your Claude "give me a tour of the agents" — it walks each one and explains it in plain English.
Pick one small repetitive thing in your week and ask Claude to automate it. Fastest way to learn the build loop.
When something comes up.
Your Claude, in the folder. It knows every agent.
Follow CREDENTIALS.md. Only pull in Matt if the doc says so (e.g. adding you to Google Ads).
That's a Matt one.