Three layers, one session
A coding session looks like one thing. It is three: the editor you type in, the harness that decides how the session is coordinated, and the model provider that answers. A model that still works through another endpoint does not prove the harness path still works.
| Layer | What it decides | Where it lives |
|---|---|---|
| Editor | Where you type, and which extensions run. | VS Code, Cursor, VSCodium, Insiders. |
| Harness | How the agent session, tools, and permissions are coordinated. | Editor and agent settings. |
| Provider | Which model answers, and through which endpoint. | Keys, base URLs, or a local server. |
The Local harness is being retired. The useful question is not whether your model still works. It is whether your session still starts the way you think it does.
Run this
Audit your editor's harness settings without changing them.
Copy snippet
import os, pathlib, platform, re
home = pathlib.Path.home()
editors = ["Code", "Code - Insiders", "Cursor", "VSCodium"]
paths = []
for name in editors:
if os.name == "nt":
paths.append(pathlib.Path(os.environ["APPDATA"]) / name / "User" / "settings.json")
elif platform.system() == "Darwin":
paths.append(home / "Library/Application Support" / name / "User" / "settings.json")
else:
paths.append(home / ".config" / name / "User" / "settings.json")
pattern = re.compile(r'"([^"]*(?:harness|sessiontarget)[^"]*)"\s*:\s*("(?:[^"\\]|\\.)*"|true|false|null)', re.I)
for path in paths:
if not path.is_file():
continue
text = path.read_text(encoding="utf-8", errors="replace")
found = pattern.findall(text)
print(path)
print(" no harness-related keys" if not found else "\n".join(f" {k} = {v}" for k, v in found))
Open full example
The complete script, with the cross-platform settings paths and a short summary.
audit-harness.pyPython 3.15.2 · no dependencies
View source
The upstream change, and the local script this example uses.
GitHub changelog View audit-harness.pyCheck your result
settings.json: no harness-related keys
Tested 2026-11-17 · Python 3.15.2 · macOS 27.3
The script scans the default settings paths for VS Code, Insiders, Cursor, and VSCodium. It does not inspect extension storage or a portable install. Your output may name a different editor or show a harness key.
Read the result
The audit prints only key names and values that contain “harness” or “sessiontarget.” It never prints the whole settings file. Three outcomes matter:
- No harness-related keys
- Your settings do not override the default harness. That is not proof you are on a supported path; check the editor and extension version.
- A Local harness setting
- Something like
vscode.temporaryDefaultToLocalHarnessor a session target oflocalis explicit. Put a migration date on it. - An endpoint or base URL
- That is the provider layer. It tells you where the model comes from, not which harness coordinates the session.
Hand it to your agent
A snippet alone is not the whole job. The audit has to see your editor, your extensions, and your provider. Copy the prompt below into your coding agent; it tells the agent how to inspect your setup and adapt the audit to your use case.
Agent prompt
Paste this into the coding agent you already use. It is written to inspect before editing and to stop at the approval boundary.
You are auditing my coding-agent setup. Work read-only until I approve changes.
1. Identify my operating system, editor and version, installed agent extensions, and the model endpoint my agent uses.
2. Locate the harness or session-target settings in my editor and agent configuration. Check the usual settings paths and any portable or profile-specific install.
3. Run the audit logic from ./audit-harness.py, or inline the same check. Report every harness-related key and its value.
4. Explain which layer each finding belongs to: editor, harness, or model provider. Do not print API keys, tokens, or credential-bearing URLs. Report hosts only.
5. If a deprecated Local harness setting is present, propose the smallest migration. List exact files and commands, and wait for my approval before editing anything.
6. Finish with a one-page report: current state, risk, recommended change, verification step, and what you could not verify.
Make the change
Do not migrate just because a date exists. Update the editor or extension first, then check whether the harness default changed. Keep the provider configuration separate from the harness setting. Verify a real session, including tool calls and permissions, before you call it done.
- Record the editor and extension versions before and after the change.
- Keep the provider endpoint and the harness preference in separate settings.
- Verify a real session with tools, not only a chat reply.
- Keep a rollback note with the previous setting and the date.