This guide takes you from a Mac with nothing on it to your first story merged, in six steps: set up your machine, understand its credentials, plan work, build it, release it, and fix what goes wrong. Each page says what you will do, the steps, what you should see, and what to do when something goes wrong. Follow the pages in order the first time.
Setting up someone else? An admin grants a new developer's GitHub and AWS access with one command before they start: see For admins: access, keys and stages.
~/dev/devstride, and wt1 and wt2 beside it for agents), each running the app locally in Docker with its own demo data, plus your machine's own AWS stage for testing against real AWS services. One command proves it all works: ds machine ready./devstride:* commands that plan, build, review and release work.| Part | Time | Needs you? |
|---|---|---|
| Set up your machine | Plan for about an hour and a half on a blank Mac, from one pasted line. Most of it is downloads (Docker Desktop and the other tools), the first build of the demo data, and your AWS stage's first deploy (about half an hour) | For the first part: a few questions, one y, your Mac password (twice on an agent machine) and some browser sign-ins. Once the demo data starts building, setup needs nobody |
| Credentials and access | Ten minutes to read | No: setup fetches the team's keys for you |
| Plan work | Depends on the work | Yes: you make the planning decisions; the agent drafts and records them |
| Develop | About a day per story | Only at decisions the agent cannot make |
| Release | As long as its review takes; agents run it | The owner says yes to every production release |
There are two kinds of DevStride machine. Setup is the same command for both; it asks which one this is.
Setup installs and configures everything it can by itself. It stops only for what a person must do: type a Mac password, approve a sign-in in a browser, and answer one Proceed? [y/N], which also covers the changes to what your agents may do without asking. Before you start, an admin gives you your GitHub and AWS access, and you set your AWS password. Afterwards, you enable Claude in Chrome with one click. Each of these is named on the setup page, and setup says exactly what to do when it reaches one.
After setup, agents do most of the building. You decide what to build, answer the questions only you can answer, and say yes to releases.
The guide is the path through. The pages under Intro and Agentic Skills are the reference behind it: every command, rule and setting in depth. The guide links to them wherever you want more.
Next: Set up your machine
Meetings
Pull Outlook calendar events and Microsoft Teams calls into Weekly Logs and log them against tasks in a couple of clicks.
Set up your machine
From a Mac with nothing on it to READY with one pasted line: what to have ready, what setup asks, what it installs, your own AWS stage, and what to do after.