⏱ About 15 minutes · do this before the training

Set up Claude Code on a TechLoq computer

(and maybe other 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.

You'll fix two small things:

Open a few websites — you (or whoever manages your filter) tell the filter to allow them.
Set up 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 the 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). Either way, Step 2 collects the ones you need to send to your filter.

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

Click the link. If it opens, you're fine. It's already in the Step 2 list you'll send, so there's nothing else to do here.

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

Send your filter the list of sites

Run the test in Step 1 first. A ready-to-send message then appears here with the sites that didn't open, plus the few this page can't check — copy it and send it to your filter company (ask for permanent access). For TechLoq: open the app → Support & Help → Contact Us (or Request Access on a block page → “entire website,” “permanent”).

Set up the trust file (certificate)

Your coding tools don't yet trust your filter the way your browser already does. This small file fixes that.

Two downloads, then run the setup tool:

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

Then open your Downloads folder, find techloq-setup.cmd, and click it to run it. It walks you through the rest.
If Windows shows a blue “Windows protected your PC” box, click More info → Run anyway.

😌 Nothing scary happens. When you run it, it explains what it's going to do, then asks for your OK before it changes anything. It installs nothing, needs no admin, and is fully reversible.

It didn't run / 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 .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-ca.cer"
setx SSL_CERT_FILE       "C:\Users\YOU\Downloads\techloq-ca.cer"
setx NODE_EXTRA_CA_CERTS "C:\Users\YOU\Downloads\techloq-ca.cer"
pip config set global.cert "C:\Users\YOU\Downloads\techloq-ca.cer"
git config --global http.sslCAInfo "C:\Users\YOU\Downloads\techloq-ca.cer"
npm config -g set cafile "C:\Users\YOU\Downloads\techloq-ca.cer"

then close and reopen your terminals.

What does the setup tool do?

It shows you the certificate's name and fingerprint so you can confirm it's really your filter's, saves a copy of it in a safe folder (so clearing your Downloads won't break anything), points your coding tools at that copy, then checks they work. It shows you the plan and asks for your OK before it changes anything. It saves a backup so you can undo anytime. Curious? At the “set this up?” question, type D to see the exact technical details.

🔍

How do I know it worked?

After you've done the steps above, run this quick check. It only checks — it changes nothing — and tells you plainly whether you're ready.

⬇ Download the “Did it work?” test

Find techloq-test.cmd in your Downloads and click it to run it. A black window opens and shows one of:

SUCCESS! Everything works — you're ready. Nothing else to do.
Not ready yet — it names the one thing to fix and which step to go back to.

If Windows shows a blue “Windows protected your PC” box, click More info → Run anyway. Haven't installed Python/Node/Git yet? That's fine — the check confirms your certificate is set up and ready for them.

✓

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 site list to my filter companyThe list from Step 2

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 tool and it passedRan techloq-setup.cmd in Step 3

＋

More help (optional)

Undo / remove this setup

Want to undo the setup? Download this and click it to run it. It puts your coding tools back the way they were before. It asks for your OK before changing anything.

⬇ Download the remove tool

After it runs, close and reopen your terminals. If Windows shows a blue box, choose More info → Run anyway.

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

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

If something goes wrong

A website still says it's blocked	Do Step 2 — send the message to your filter and ask for “permanent” access.
It says it couldn't use your file	Run the setup tool again and pick the file you got from cert.techloq.com.
You want to undo it	Download the “Remove tool” above and run it.
It worked before, now everything errors	Your filter probably updated its certificate — get the new one from cert.techloq.com and run the setup tool again.

For IT / security teams

Plain summary of exactly what the setup tool (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 site analytics or intentional telemetry. No analytics package, tracking, cookies, or external scripts. (The host, Cloudflare, keeps normal request logs like any website, and each “Test” probe makes an ordinary request to the site being tested, so that request metadata is visible to those sites — as with any browser.) The script's only 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 (Windows can't cryptographically verify who published them or whether they were altered after download); 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. Run it, then use the ready-made message below.
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.
The certificate is the filter-specific part. If your filter company gives you a certificate file, the “by hand” steps under Step 3 still apply — just point them at their file instead of TechLoq's.

Send your filter company this message — it fills in with your blocked sites and the certificate question:

Run the test in Step 1 first — this message then fills in with the sites you need, plus the certificate question.