Settings for staff machines
StackJack can make the settings file that each AI coding tool reads on a staff computer. The file points the tool's usage reporting at StackJack. If you choose, it also limits which MCP servers the…
Written By Christopher Scaminaci
Last updated 13 days ago
StackJack can make the settings file that each AI coding tool reads on a staff computer. The file points the tool's usage reporting at StackJack. If you choose, it also limits which MCP servers the tool may use. You download the file or let StackJack deliver it. This page covers the files, where they go, the token inside them and what the coverage panel means.
At a glance
- Plan: every plan.
- Who: a governance administrator. An auditor can read the page. Downloads need an administrator who signed in with a second factor.
- Where you set it up: AI Governance → Staff computers → Coding tools. The Windows endpoint agent has its own page, Staff computers → Endpoint agent. The Portal calls this page Coding tools.
- Where you see the data: the facts appear in Activity → Activity explorer. The coverage panel on the same page shows who runs your settings.
This is different from the Windows endpoint agent. See The StackJack endpoint agent.
What StackJack makes
From your organization's policy, StackJack makes the settings file for each AI coding tool you choose: Claude Code, Codex, VS Code Copilot and Gemini CLI. The same policy also makes the files that install the browser extension on Chrome, Edge and Firefox. See Installing the browser extension. You choose how far to go with MCP servers:
- Monitor only. The settings carry no MCP rules. Staff keep using any MCP server.
- Block the servers I denied. The settings block every server on your denied list. Everything else keeps working.
- Allow only the servers I approved. The settings allow the servers on your approved list and block everything else. A server known only by name cannot be enforced until you add its address or command, and the page lists those. If no server is approved yet, this choice would block every MCP server on every machine, so the page asks you to type a confirmation phrase first.
What the settings report follows the capture level you chose for the source. At Facts only, no prompt or response text leaves the machine. At the levels that scan or store text, the tool is told to send it so that your scanning rules can run.
Where each file goes
Install by hand
Download the file from the page. Then, on Windows, open PowerShell as an administrator and copy the file to its place. For example:
New-Item -ItemType Directory -Force -Path "C:\Program Files\ClaudeCode" | Out-Null; Copy-Item "$env:USERPROFILE\Downloads\<downloaded file>" "C:\Program Files\ClaudeCode\managed-settings.json" -Force
On macOS and Linux:
sudo mkdir -p "<folder>" && sudo cp ~/Downloads/<downloaded file> "<full path>"
For the registry file, run reg import "<downloaded file>". For a profile, use open <downloaded file> or deliver it with your MDM. The page shows the exact command for each file.
To avoid doing this on every machine, see Delivering the settings through your RMM.
The token inside the settings
Every machine that receives these settings sends its usage with one token that StackJack made for your organization. The token can only send usage to StackJack. It cannot read anything.
- Rotate makes a new token. The old one keeps working for seven days, so machines that have not updated yet still report.
- Revoke now stops the old one at once.
Because the settings hold the token, each download is recorded in your audit log and needs an administrator who signed in with a second factor.
What each coverage state means
Claude Code reports which settings it runs, without saying which computer it is on. So StackJack shows coverage for each person, and compares what each person's Claude Code reports with the settings StackJack made. For the state of each machine, read the result of the push in your RMM and on the target's runs.
- Runs the current settings. Claude Code reported the settings StackJack made for the policy's newest version.
- Runs an older version. Claude Code reported settings StackJack made earlier. A push has not reached it yet.
- Runs settings that are not StackJack's alone. Another managed source is present beside, or instead of, StackJack's file.
- Runs no managed settings. Claude Code started with no managed source at all.
- Claude Code refused the settings. Claude Code refused to start with the settings.
- Uses Claude Code but does not report. Claude Code activity arrived in the last 7 days, but no settings report did.
The settings report is not AI activity. It does not make a person count towards your staff count.
Limits to know
- Codex reports usage per user on Windows, because Codex has no system-wide settings place there.
- In VS Code, environment variables set on a machine can override the managed values.
- At Facts only, MCP server names reach StackJack as "custom" or "third-party", so StackJack cannot list the exact server. Raise the capture level or add the server by hand.
- StackJack writes only settings the vendor documents. VS Code Copilot gets both MCP lists (an allow list and a deny list). Gemini CLI gets an allow list only, because its deny list names a server and a person can give the same server another name. Codex gets an allow list only, because it documents no deny list.
- Gemini CLI follows your allow list by defining each approved server in its system settings. A server a person already runs under an approved name then uses your definition, so their own login details for it stop applying. An approved tool known only by name is not listed for Gemini CLI, Codex or VS Code Copilot, because a name is not a control.
- For an EU or UK organization, StackJack reads your directory, your vendors' member lists and your Microsoft apps only once your staff notice is in place.
Troubleshooting
Next
Was this helpful?
More in Connect your AI
Data sourcesRead your AI vendors' admin accountsMicrosoft 365 Copilot and AzureGemini activity and Gemini conversationsStill need help? Ask the team