For you and your IT team
Technical requirements
The Anthropic FDE Residency starts with three hands-on days in person, then the Final Practical, which you do remotely. You build an AI agent in Python on your laptop with Claude Code. The setup pack checks this page and writes an IT ticket for any gap.
Laptop
- macOS, Windows or Linux. The laptop you will use all week. About 5 GB free.
- You can install software as a normal user, without administrator rights.
- A
bcdevfolder in your home folder, not in Downloads, OneDrive, iCloud or Dropbox. - A working camera and microphone.
Laptop options: A) your company laptop (preferred). B) Your personal laptop, if your company allows it. C) Last resort: a program Chromebook, if you tell your hosts at least 2 weeks before the cohort. With B or C, your company's Claude sign-in rules must still let you sign in from that device, so tell your IT team which one you will use.
Software
No administrator rights are needed if Python and git are already installed. If they are not, your IT team may need to install them.
| Item | Notes |
|---|---|
| Python 3.11 to 3.14 (3.12 or 3.13 is best; 3.15 is too new), with pip and venv. | For the labs. |
| git, with your name and email set. | Local commits only. |
| Claude Code, installed. | You sign in on Day 1 with the provided API key. Git for Windows is optional. |
Not needed: Node.js, Docker, WSL, make.
Accounts
| Account | Notes |
|---|---|
| An Anthropic API key. | Provided by the program, via BTS, on Day 1, for Claude Code, the labs and the Final Practical. For the key you need no Console account. You may bring your own key if you prefer. |
| A Claude seat in your own company's Claude organization, on your work email. Required. | Provided and paid for by your company, and set up by your IT team before the setup date. Claude Academy needs it. 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. If your company does not use claude.ai, tell the program team now. |
| Claude Academy, academy.claude.com. Required. | The course for the Week. Once IT has set up your seat: on your company network or VPN, sign in to claude.ai with your work email, open claude.ai/invites and accept the invite to Claude Frontier Academy. Then sign in at academy.claude.com, choose Claude Frontier Academy (not your company) and press Authorize. Open the course and press Start course, even if the lessons already show, because that is what enrolls you. Do this before you travel. |
| The course portal, app.fde-residency.com. | Your registered email. The code comes from noreply@notify.cloudflare.com. |
| Slack, fde-residency.slack.com. | Required for the 12-week Fellowship after the Week; encouraged but not required for the Week itself. A personal email is fine. The invite is in your welcome email. |
| Microsoft Forms. | Tested by the setup check. The surveys, the quiz and the Final Practical run on practical.fde-residency.com. If Microsoft Forms is blocked, the setup check shows a failure: tell the program team. |
Network
Outbound HTTPS (port 443) to these hosts, on the network you bring.
| Purpose | Hosts |
|---|---|
| Anthropic, all week. | api.anthropic.com platform.claude.com claude.ai claude.com academy.claude.com downloads.claude.ai code.claude.com |
| Claude Academy sign-in and course, by the setup date. | claude.ai and *.claude.ai claude.com and *.claude.com (includes academy.claude.com and sso.claude.com) anthropic.com and *.anthropic.com hcaptcha.com *.hcaptcha.com challenges.cloudflare.com accounts.google.com (only if you sign in with Google) |
| Course portal, all week. | fde-residency.com www.fde-residency.com app.fde-residency.com setup.fde-residency.com btsgroup.cloudflareaccess.com |
| Surveys, quiz and the Final Practical. | practical.fde-residency.com |
| Setup installs, once. | pypi.org files.pythonhosted.org www.python.org git-scm.com |
| Microsoft Forms, all week. | forms.cloud.microsoft forms.office.com |
| Slack. | slack.com and its subdomains *.slack-edge.com slack-imgs.com *.slack-imgs.com slack-files.com slackb.com |
| Google Meet. | meet.google.com accounts.google.com apis.google.com apps.google.com clients2.google.com clients4.google.com clients6.google.com meetings.clients6.google.com *.googleapis.com www.gstatic.com fonts.gstatic.com lh3.googleusercontent.com One more Google host is in the full requirements document (see For IT below). For best quality, also UDP 3478 and 19302 to 19309. |
| Zoom. | zoom.us *.zoom.us zoom.com *.zoom.com Also TCP 8801 and 8802, and UDP 3478, 3479 and 8801 to 8810. |
Email from @slack.com, @slack-mail.com, noreply@notify.cloudflare.com and the whole mail.anthropic.com domain must not be quarantined. Claude invitations and sign-in links come from varying addresses there, and invitations expire after 21 days.
A proxy that rewrites TLS works in the browser if the company root certificate is trusted. Python, pip and git also need that root as a PEM file. A proxy that asks for a login (HTTP 407) needs signing in first, and command-line tools may need an exemption for these hosts.
If your company limits which Slack workspaces staff can join, add fde-residency.slack.com.
Local ports
Python must be able to listen on 127.0.0.1, ports 3001, 8000, 44781 to 44784 and 8642.
What the setup check does
setup.py is one Python file, no dependencies. It makes the bcdev folder and a virtualenv, installs pinned packages from PyPI, checks this page and writes env-report.md. Nothing system-wide, never as administrator. From Day 1 it also checks your key with one API call.
After the Week
The 12-week Fellowship needs Slack, Google Meet and Zoom, for the community, office hours and expert sessions. If one is blocked, you can do the Week but not the Fellowship. Slack does not need a work email. A personal email works if your company allows it.
For IT
Your company's program contact has the full technical requirements document from the program team. It covers Claude seats, single sign-on, Tenant Restrictions, hosts and email, a test with one learner, and the checklist to send back one week before the program. Every step in it must be done before Day 1, or your engineers cannot take part.
The setup check's report ends with a ticket listing the failed rows and the exact hosts or settings to unblock. Please turn it around within a few days, or the participant tells the hosts before Day 1.