Prerequisites
What you need before you start the 30-minute walkthrough.
You'll need a few things in place before deploying EasyCC.
A test machine
Pick a Windows or macOS machine you can install on, change settings on, and uninstall from without affecting real users. A VM works well.
| Platform | Minimum |
|---|---|
| Windows | Windows 10 or 11. WebView2 runtime must be installed (preinstalled on most modern Windows). |
| macOS | macOS 12 or later (Intel or Apple Silicon). |
Linux isn't supported in v1.
An MDM or local-admin access
You need a way to push managed configuration to the machine. The walkthrough shows three options — pick whichever you have:
- Microsoft Intune — for Windows fleets.
- Jamf Pro (or another macOS MDM that writes to
/Library/Managed Preferences/) — for macOS fleets. - Direct registry / plist edit — when you don't have an MDM available, you can write to the same locations by hand. Useful for the lab walkthrough.
You'll also need either an EV-signed installer (we provide one) or local admin rights to install EasyCC on the test machine.
Network access
EasyCC and the test machine need to reach a few hosts during install and on every launch. See Network endpoints for the full list — for the walkthrough, you mainly need:
- The download host (
easycc.appor your mirror) - Anthropic's API (
api.anthropic.com) - Supabase (for sign-in) — your IT may have allowlisted this already
If you're behind a proxy or air-gapped, jump to Self-hosted mirror before starting the walkthrough — you'll need a mirror in place first.
A managed-policy field you want to set
Pick one to test. Good first picks:
| Field | Why it's a good test |
|---|---|
release_channel | Easy to see — appears in Settings → About immediately. |
dev_mode | Visible in the file tree (hidden files toggle). |
max_update_deferral_hours | Visible in the update dialog. |
You'll set this in Push your first policy.
Next
How is this guide?