⏱ About 15 minutes · do this before the training

Set up Claude Code on a TechLoq computer

(and maybe other kosher filters too — see the bottom of the page)

Your filter blocks a few things Claude Code needs. This page fixes that — and checks your work as you go. No tech background needed.

Here's the whole idea in plain terms:

A content filter keeps your internet safe, but it also blocks some of the websites and secure connections that coding tools rely on. To use Claude Code, you fix two small things:

Open a few websites — you (or whoever manages your filter) tell the filter to allow them.
Install one "trust file" — a small certificate so Claude Code's tools connect smoothly.

Just work down the page. It tests things for you and tells you exactly what's left.

🧩 These exact steps are written for TechLoq — the most common filter here. On a different filter (GenTech, NetSpark, and others)? Step 1's website test still works for you exactly the same. Only the “trust file” part is different — see “On a different filter?” at the bottom before your training.

See which websites open

Click the button. Green = it opens. Amber = your computer couldn't reach it (usually blocked). You don't need to know what any of these are.

Amber means your computer couldn't reach it — usually the filter is blocking it (a few sites just don't answer quick pings). Step 2 turns the amber ones into a ready-to-send message.

👆 One site we can't test for you — please check it yourself:

Click the link. If the page opens, you're fine — leave the box unticked. If you get a “blocked” page, tick “didn't open” and it's added to your email in Step 2.

This checks websites only. It can't check the “trust file” from Step 3 — that gets checked for you when you run the helper there. So even if everything is green, still do Step 3.

Ask your filter to open the ones that didn't

Run the test in Step 1 first. If anything comes back amber — or you tick a “didn't open” box — a ready-to-send message appears here.

Install the trust file (certificate)

For safety, TechLoq re-locks every secure website with its own key. Your web browser already recognizes that key — but the behind-the-scenes tools Claude Code uses don't yet. This one small file teaches them to.

Two downloads, then run the helper:

① Get the trust file (opens cert.techloq.com) ② Download the setup helper

Then open your Downloads folder, find techloq-setup.cmd, and click it to run it. It explains everything else itself.
If Windows shows a blue “Windows protected your PC” box, click More info → Run anyway.

😌 Nothing scary happens. The helper walks you through it and changes nothing until you say yes — you can just look and type N. It installs nothing, needs no admin, and saves a one-click undo.

The double-click didn't work / I want to do it another way

Two other options:

Run the PowerShell version: download techloq-setup.ps1, then right-click it → Run with PowerShell. (If you don't see “Run with PowerShell,” use the double-click .cmd above instead — it avoids this.)

By hand: save the trust file, then paste these into a terminal one at a time (replace the path with where you saved it):

setx REQUESTS_CA_BUNDLE "C:\Users\YOU\Downloads\techloq.crt"
setx SSL_CERT_FILE       "C:\Users\YOU\Downloads\techloq.crt"
setx NODE_EXTRA_CA_CERTS "C:\Users\YOU\Downloads\techloq.crt"
pip config set global.cert "C:\Users\YOU\Downloads\techloq.crt"
git config --global http.sslCAInfo "C:\Users\YOU\Downloads\techloq.crt"
npm config -g set cafile "C:\Users\YOU\Downloads\techloq.crt"

then close and reopen your terminals.

What does the helper actually do?

It saves a copy of your trust file in a safe folder (so clearing your Downloads won't break anything), points your coding tools at that copy, then checks they work. Before it changes anything it shows you the plan and asks — say N and nothing changes. It saves a backup so you can undo anytime, and it installs nothing. Curious? At the “set this up?” question, type D to see the exact technical details.

⚠️ If someone suggests a “quick fix” that turns off security checking, don't use it — it leaves your computer unprotected. The trust file above is the safe, correct way.

✓

Your progress

Some boxes tick themselves as you go. Tick the rest yourself once you've done them — your progress is saved on this device.

Tested my websitesTicks automatically when you run Step 1

Sent the list to my filter companyOnly needed if Step 1 showed any amber

All my websites now openTicks automatically when a test comes back all green

Downloaded the trust fileFrom cert.techloq.com in Step 3

Ran the setup helper and it passedDouble-clicked techloq-setup.cmd in Step 3

＋

More help (optional)

The complete list of sites (for a filter admin who wants it all at once)

The test up top already flags what you need. This is the full reference if someone wants to allow everything in one go. A first-time user only needs the “required” set — the rest are per feature.

Required to install & run Claude Code (everyone):

api.anthropic.com          the AI itself
claude.ai                  signing in
claude.com                 sign-in page
platform.claude.com        sign-in / accounts
downloads.claude.ai        installer & updates
registry.npmjs.org         installing Claude Code
nodejs.org                 installing Node.js

Only if you'll use that tool or feature:

Git & GitHub    github.com, codeload.github.com,
                objects.githubusercontent.com,
                raw.githubusercontent.com, git-scm.com
Python          pypi.org, files.pythonhosted.org
Supabase (DB)   api.supabase.com, *.supabase.co
Gmail / Google  accounts.google.com, oauth2.googleapis.com,
                www.googleapis.com
Cloudflare      api.cloudflare.com, *.pages.dev
here.now        here.now, *.here.now
HubSpot         api.hubapi.com, app.hubspot.com

Based on several organizations' real projects plus Claude Code's required hosts.

If something goes wrong

A site still shows a “blocked” page	Finish Step 2 — send the message to your filter and choose “permanent.”
The helper says it “didn't trust the certificate”	Run it again and pick the file you downloaded from cert.techloq.com.
Claude Code still won't connect after setup	Close every black terminal window (and Claude Code) and reopen them, so the change takes effect.
You changed your mind	Double-click the “techloq-restore…” file the helper saved in Downloads to undo everything.
It worked before, now every site errors	Your filter may have refreshed its certificate — download it again from cert.techloq.com and run the helper once more.

For IT / security teams

Plain summary of exactly what the setup helper (techloq-setup.cmd / .ps1) does, for review before it's run on a managed machine:

Scope: current user only. Sets three per-user environment variables (REQUESTS_CA_BUNDLE, SSL_CERT_FILE, NODE_EXTRA_CA_CERTS) in HKCU\Environment, plus per-user pip/git --global/npm -g config. No elevation. It does not write to the Windows system root store, and does not affect browsers or other users.
Purpose: points the dev toolchain (Python, Node, Git) at the filter's root certificate so those tools can validate TLS that the filter re-signs. This is required to operate behind a TLS-intercepting filter.
Copies the certificate into a per-user folder (%LOCALAPPDATA%\ClaudeCodeTechLoq) so the tools don't depend on the Downloads folder. Installs no software, downloads nothing else, deletes nothing. The certificate itself is downloaded by the user in the browser from their filter provider (e.g. cert.techloq.com).
No telemetry. No analytics, tracking, cookies, or external scripts. The page's “Test” makes reachability probes to the listed developer hosts only; the script's sole network calls are post-setup validation to pypi.org, registry.npmjs.org, and github.com.
Reversible. Before applying, it captures prior values and writes a timestamped techloq-restore-*.ps1 to Downloads; running it reverts every change.
Does not weaken TLS. No NODE_TLS_REJECT_UNAUTHORIZED=0, no --trusted-host, no disabling of certificate verification.
Tradeoff to note: trusting the filter's interception CA lets the filter operator inspect (and technically alter) the dev tools' HTTPS traffic. Confined to that user's dev toolchain.
Distribution caveats: the scripts are unsigned; the .cmd launches PowerShell with -ExecutionPolicy Bypass and runs its own embedded script, which may trigger SmartScreen or EDR. Review the source (it's plain text) before wide deployment.

On a different filter? (not TechLoq)

Lots of filters are used in our community — you might have GenTech, NetSpark, Meshimer, Geder, MB Smart, Jnet, Rimon, Netfree, or another (some are installed through TAG). Here's what carries over and what doesn't.

Step 1 (the website test) works for you exactly the same. A blocked site shows amber no matter which filter you have. So run it, and send your filter company the list from Step 2.
Step 3 (the trust file) is the part that differs. The download link cert.techloq.com is TechLoq-only. Other filters that inspect secure traffic have their own certificate and their own way to install it — and a few don't need one at all. For example, GenTech (built on Livigent) uses an “SSL Override” / URL-approval system in its app.
What to do before the training: contact your filter company and ask the two questions in the message below. If they give you a certificate file, the “by hand” steps under Step 3 still apply — just point them at their file instead of TechLoq's.

Message to send any filter company:

Hi, I'm setting up software-development tools (Claude Code) on my
filtered computer. Two questions:

1) Please give permanent access to these websites:
   api.anthropic.com, claude.ai, claude.com,
   platform.claude.com, downloads.claude.ai,
   registry.npmjs.org, nodejs.org

2) Do your tools need a security certificate installed so programs
   like Python, Node.js and Git can trust filtered connections?
   If yes, how do I download and install it?

Thank you!