Before Day 1 · About 30 minutes
Get ready for the Week
Do this about a week before Day 1, one screen at a time. You do not need an API key yet.
Which laptop will you use during the Week?
During the intensive week you will be hands-on building, so you need a laptop to work on. There are three options. Option C requires two weeks' notice through the person coordinating your participation at your company.
Not sure which applies? Ask the person coordinating your participation at your company.
Install Claude Code
Follow the install steps for your computer on the Claude Code install page. Do not sign in yet.
On Day 1 the program gives you an API key. You put it in your week folder's .env and run python3 setup/setup.py --claude-key from build-along (Windows: python setup\setup.py --claude-key), which lets Claude Code read it from there. You do not need a Console account, and you do not sign in to Claude Code with a Claude account. You may bring your own key if you prefer.
Read this before Day 1. How Claude Code picks up an API key, and how to check which sign-in it is using: Manage API key environment variables in Claude Code.
Work laptops sometimes block installs. If this step fails, carry on to the next step anyway. The setup check writes an IT ticket that covers it.
Download the setup pack and run it
Unzip it. Open a terminal in the unzipped bcdev-env-setup folder and run python3 setup.py. On Windows, run python setup.py.
It takes 5 to 20 minutes and pauses once so you can sign in to the program site, app.fde-residency.com, which carries the hands-on pack and the room tools. This is not Claude Academy, which comes later. The API key row says Day 1. That is expected. Leave it running and go to the next screen.
On Day 1 you put the key in the .env file the setup pack makes. If you already have ANTHROPIC_API_KEY set in your terminal from other work, it takes priority over other sign-ins. This article shows how to check it and unset it.
Run it on the laptop you will actually bring, and check with your company that a personal laptop is allowed before you rely on it.
SHA-256 of the zip, for your IT team: 1097e7214900f74ef1bb6e08227d0f2f5fcab1bf00559e01a5cf3ee6b47424d1
Request a program device now
Tell the person coordinating your participation at your company that you need a program device, at least two weeks before Day 1. They pass the request to the program team. Do it today.
There is nothing to install. The device is ready on Day 1 with Claude Code, Python and your API key set up. The Final Practical happens after the Week, away from the venue, so ask at the same time what you will use for it.
If option A or B becomes possible later, come back, change your answer on the first screen, and run the setup check.
Read the SUMMIT briefing
On Day 1 you join SUMMIT, an invented bank, as its new engineer, and every session that week is a piece of work for SUMMIT. The briefing introduces the client, the people you will work with and the problem you solve each day. About 10 minutes. Read it before Day 1.
You can read it while the setup check from the last screen is running.
Accept your Claude Academy invite
The Week runs on Claude Academy, Anthropic's learning site. You need a seat in your own company's Claude organization, on your work email, which your company provides and your IT team sets up first. Then you get an invite to the Claude Frontier Academy organization on Claude, at your work email. It takes about five minutes. Do it before you travel, on your company network or VPN, on a work device if you have one.
- Sign in to claude.ai with your work email, open claude.ai/invites and press Accept invite for Claude Frontier Academy.
- Sign in at academy.claude.com. Choose Claude Frontier Academy, not your company, and press Authorize. Already signed in? Click your avatar, then Switch organization.
- Open the course and press Start course, even if the lessons already show, because that is what enrolls you. You are done when the first lesson opens.
If your company cannot give you a seat in time, a personal Claude account is the fallback, only if your IT team agrees, and the program team sends you different steps. No invite by the Friday before Day 1, or it will not open? Check your spam and your company's email quarantine, then reply to your welcome email. Do not leave it until Day 1.
After the Week, the Final Practical runs on its own site, practical.fde-residency.com. Your hosts explain it on the last day in the room.
Last thing: read your report
When the setup check finishes, the report is env-report.md in your new bcdev folder. Keep it there. If every row says PASS, you are ready for Day 1.
Did a check fail?
Send the technical requirements page to your IT team, together with the IT ticket from the end of your report. Do it today. IT tickets take days. Run setup again after the fix. If IT cannot unblock you before Day 1, tell the person coordinating your participation now so option C can be arranged.
A Slack or Google Meet warning does not stop the Week. It stops the Fellowship after the Week. Send the ticket for those too.
Checklist
- Claude Code installed (or the failure is in your IT ticket)
- Setup check run on the laptop you will bring
- Every row in
env-report.mdsays PASS (or the failure is in your IT ticket) - SUMMIT briefing read
- Claude Academy invite accepted, and the course opens at academy.claude.com (the invite may come later)
That is everything until Day 1.
You are set for now
Checklist
- Your company's coordinator told that you need a program device, at least two weeks before Day 1
- Asked what you will use for the Final Practical after the Week
- SUMMIT briefing read
- Claude Academy invite accepted, and the course opens at academy.claude.com (the invite may come later)
If a company or personal laptop becomes possible, come back and change your answer on the first screen. Otherwise, that is everything until Day 1.