llm-switcher 1.1.0

package/blindfold/make-certs.sh

@@ -0,0 +1,88 @@
+#!/usr/bin/env bash
+# Build the private CA and the leaf certificate that blindfold.mjs presents.
+#
+# Windows: run this from Git Bash. The openssl that ships with Git for Windows works.
+# The earlier attempt used PowerShell New-SelfSignedCertificate, whose leaf was refused
+# with "unsuitable certificate purpose" because it carried no serverAuth extended key
+# usage. The extension files below are what fix that, so do not drop them.
+#
+# Subjects come from a config file instead of -subj: Git Bash rewrites any argument
+# that starts with a slash, so "/CN=..." would arrive as "C:/Program Files/Git/CN=...".
+#
+# Nothing here touches a system trust store. Codex trusts this CA through the
+# CODEX_CA_CERTIFICATE environment variable, which the switcher exports for you.
+set -euo pipefail
+
+HOST="${1:-chatgpt.com}"
+OUT_DIR="${2:-$(cd "$(dirname "$0")" && pwd)/certs}"
+CA_DAYS=3650
+LEAF_DAYS=825
+
+# Every file here is private, and the CA key signs for any host. A directory that another
+# account created first (the /tmp recipe) could expose the key or hold planted symlinks.
+umask 077
+mkdir -p "$OUT_DIR"
+OWNER="$(stat -c %u "$OUT_DIR" 2>/dev/null || stat -f %u "$OUT_DIR")"
+if [ "$OWNER" != "$(id -u)" ]; then
+  echo "[blindfold] refused: $OUT_DIR is owned by uid $OWNER, not by you. Use a directory you own." >&2
+  exit 1
+fi
+chmod 700 "$OUT_DIR"
+
+# Build in a private work directory and move the results into place last. A failed run then
+# keeps the previous working set, and mv replaces a planted symlink instead of writing through it.
+WORK="$(mktemp -d "$OUT_DIR/.build.XXXXXX")"
+trap 'rm -rf "$WORK"' EXIT
+
+echo "[blindfold] host   : $HOST"
+echo "[blindfold] output : $OUT_DIR"
+
+cat > "$WORK/ca.cnf" <<EOF
+[req]
+prompt = no
+distinguished_name = dn
+x509_extensions = v3_ca
+
+[dn]
+CN = LLM Switcher Local CA
+
+[v3_ca]
+basicConstraints = critical,CA:TRUE,pathlen:0
+keyUsage = critical,keyCertSign,cRLSign
+subjectKeyIdentifier = hash
+# Codex trusts this CA for every host. The constraint limits a leaked ca.key to HOST and its subdomains.
+nameConstraints = critical,permitted;DNS:$HOST
+EOF
+
+cat > "$WORK/leaf.cnf" <<EOF
+[req]
+prompt = no
+distinguished_name = dn
+
+[dn]
+CN = $HOST
+EOF
+
+cat > "$WORK/leaf.ext" <<EOF
+basicConstraints = critical,CA:FALSE
+keyUsage = critical,digitalSignature,keyEncipherment
+extendedKeyUsage = serverAuth
+subjectAltName = DNS:$HOST,DNS:*.$HOST
+EOF
+
+openssl ecparam -name prime256v1 -genkey -noout -out "$WORK/ca.key"
+openssl req -x509 -new -key "$WORK/ca.key" -sha256 -days "$CA_DAYS" \
+  -config "$WORK/ca.cnf" -out "$WORK/ca.pem"
+
+openssl ecparam -name prime256v1 -genkey -noout -out "$WORK/leaf.key"
+openssl req -new -key "$WORK/leaf.key" -config "$WORK/leaf.cnf" -out "$WORK/leaf.csr"
+openssl x509 -req -in "$WORK/leaf.csr" \
+  -CA "$WORK/ca.pem" -CAkey "$WORK/ca.key" -CAcreateserial \
+  -days "$LEAF_DAYS" -sha256 -extfile "$WORK/leaf.ext" \
+  -out "$WORK/leaf.pem"
+
+mv -f "$WORK/ca.key" "$WORK/ca.pem" "$WORK/leaf.key" "$WORK/leaf.pem" "$OUT_DIR/"
+
+echo "[blindfold] CA     : $OUT_DIR/ca.pem"
+echo "[blindfold] leaf   : $OUT_DIR/leaf.pem"
+openssl x509 -in "$OUT_DIR/leaf.pem" -noout -ext extendedKeyUsage,subjectAltName

package/blindfold/wsframe.mjs

@@ -0,0 +1,176 @@
+// Minimal RFC 6455 frame reader. The blindfold capture reads a copy of the relayed bytes with it,
+// and the gateway reads the Codex WS transport with it.
+//
+// Scope on purpose: it reassembles data messages and reports control frames. It
+// does not answer a ping, does not close a connection and never writes a byte back.
+
+import zlib from 'node:zlib';
+
+export const OPCODE = {
+  continuation: 0x0,
+  text: 0x1,
+  binary: 0x2,
+  close: 0x8,
+  ping: 0x9,
+  pong: 0xa
+};
+
+const NAME = Object.fromEntries(Object.entries(OPCODE).map(([k, v]) => [v, k]));
+
+// A frame reader is a stream parser: a TCP chunk carries any number of frames, and
+// one frame can be split across chunks. It buffers until a whole frame is present.
+//
+// A message larger than maxMessage yields one {type:'error'} item, decided from the frame
+// header before the body is buffered. After an error the reader returns nothing more.
+export function createFrameReader({ inflate = false, maxMessage = Infinity } = {}) {
+  // Chunks are joined once, when enough bytes are present: joining on every chunk copies a
+  // large frame again for each chunk that carries it.
+  let pending = [];
+  let pendingBytes = 0;
+  let needed = 2;
+  let failed = false;
+  let fragments = [];
+  let fragmentBytes = 0;
+  let fragmentOpcode = null;
+  let fragmentCompressed = false;
+
+  // The sender ends each message with Z_SYNC_FLUSH and strips the empty block it
+  // leaves, so the reader appends those four bytes back.
+  //
+  // permessage-deflate uses context takeover by default: message two can reference
+  // the compression window of message one. Inflating each message on its own fails
+  // with "invalid distance too far back" from the second message onward. Measured
+  // on a real Codex stream: 20 of 22 messages were lost that way.
+  //
+  // The window is restored by passing what was already decoded as the dictionary.
+  // Raw deflate back-references reach into exactly that data, and 32 KiB is the
+  // largest window the format can address, so older output cannot be referenced.
+  //
+  // A node zlib stream would keep the context by itself, but only asynchronously:
+  // its synchronous entry point closes the handle after one call, so the second
+  // message throws. This reader is synchronous, so the dictionary is the way.
+  const TAIL = Buffer.from([0x00, 0x00, 0xff, 0xff]);
+  const WINDOW = 32768;
+  let history = Buffer.alloc(0);
+
+  const inflateMessage = (payload) => {
+    if (!inflate) return payload;
+    const opts = { finishFlush: zlib.constants.Z_SYNC_FLUSH, ...(Number.isFinite(maxMessage) ? { maxOutputLength: maxMessage } : {}) };
+    if (history.length) opts.dictionary = history.subarray(Math.max(0, history.length - WINDOW));
+    const out = zlib.inflateRawSync(Buffer.concat([payload, TAIL]), opts);
+    history = Buffer.concat([history, out]);
+    if (history.length > WINDOW) history = history.subarray(history.length - WINDOW);
+    return out;
+  };
+
+  return function push(chunk) {
+    if (failed) return [];
+    pending.push(chunk);
+    pendingBytes += chunk.length;
+    if (pendingBytes < needed) return [];
+    let buffer = pending.length === 1 ? pending[0] : Buffer.concat(pending, pendingBytes);
+    const out = [];
+    const fail = (reason) => {
+      failed = true;
+      pending = [];
+      pendingBytes = 0;
+      out.push({ type: 'error', reason });
+      return out;
+    };
+
+    for (;;) {
+      needed = 2;
+      if (buffer.length < 2) break;
+      const b0 = buffer[0];
+      const b1 = buffer[1];
+      const fin = (b0 & 0x80) !== 0;
+      const rsv1 = (b0 & 0x40) !== 0;
+      const opcode = b0 & 0x0f;
+      const masked = (b1 & 0x80) !== 0;
+      let length = b1 & 0x7f;
+      let offset = 2;
+
+      if (length === 126) {
+        needed = offset + 2;
+        if (buffer.length < needed) break;
+        length = buffer.readUInt16BE(offset);
+        offset += 2;
+      } else if (length === 127) {
+        needed = offset + 8;
+        if (buffer.length < needed) break;
+        const big = buffer.readBigUInt64BE(offset);
+        // A frame larger than 2^53 cannot be indexed by a JS number. Nothing sends
+        // one; refusing is safer than truncating the length in silence.
+        if (big > BigInt(Number.MAX_SAFE_INTEGER)) return fail('frame length exceeds Number.MAX_SAFE_INTEGER');
+        length = Number(big);
+        offset += 8;
+      }
+      const messageBytes = opcode === OPCODE.continuation ? fragmentBytes + length : length;
+      if (messageBytes > maxMessage) return fail(`message exceeds ${maxMessage} bytes`);
+
+      let maskKey = null;
+      if (masked) {
+        needed = offset + 4;
+        if (buffer.length < needed) break;
+        maskKey = buffer.subarray(offset, offset + 4);
+        offset += 4;
+      }
+      needed = offset + length;
+      if (buffer.length < needed) break;
+
+      let payload = Buffer.from(buffer.subarray(offset, offset + length));
+      buffer = buffer.subarray(offset + length);
+
+      if (maskKey) {
+        for (let i = 0; i < payload.length; i++) payload[i] ^= maskKey[i & 3];
+      }
+
+      if (opcode >= 0x8) {
+        // A control frame is never fragmented and never continues a data message.
+        out.push({ type: NAME[opcode] || `opcode-${opcode}`, payload, control: true });
+        continue;
+      }
+
+      if (opcode !== OPCODE.continuation) {
+        fragmentOpcode = opcode;
+        fragmentCompressed = rsv1;
+        fragments = [];
+        fragmentBytes = 0;
+      }
+      fragments.push(payload);
+      fragmentBytes += payload.length;
+
+      if (!fin) continue;
+
+      let body = Buffer.concat(fragments);
+      fragments = [];
+      fragmentBytes = 0;
+      let note;
+      if (fragmentCompressed) {
+        try {
+          body = inflateMessage(body);
+        } catch (err) {
+          note = `cannot inflate permessage-deflate payload: ${err.message}`;
+        }
+      }
+      out.push({
+        type: NAME[fragmentOpcode] || `opcode-${fragmentOpcode}`,
+        payload: body,
+        compressed: fragmentCompressed,
+        ...(note ? { note } : {})
+      });
+      fragmentOpcode = null;
+      fragmentCompressed = false;
+    }
+
+    pending = buffer.length ? [buffer] : [];
+    pendingBytes = buffer.length;
+    return out;
+  };
+}
+
+// permessage-deflate is negotiated in the handshake. Without this test a capture
+// would inflate a payload that was never compressed.
+export function negotiatesDeflate(headerValue) {
+  return /permessage-deflate/i.test(String(headerValue || ''));
+}

package/codex-catalog-template.json

@@ -0,0 +1 @@
+{"description":"Reliable agentic workhorse for everyday tasks.","default_reasoning_level":"medium","supported_reasoning_levels":[{"effort":"low","description":"Fast responses with lighter reasoning"},{"effort":"medium","description":"Balances speed and reasoning depth for everyday tasks"},{"effort":"high","description":"Greater reasoning depth for complex problems"},{"effort":"xhigh","description":"Extra high reasoning depth for complex problems"},{"effort":"max","description":"Maximum reasoning depth for the hardest problems"},{"effort":"ultra","description":"Maximum reasoning with automatic task delegation"}],"shell_type":"unified_exec","visibility":"list","supported_in_api":true,"priority":0,"additional_speed_tiers":[],"service_tiers":[],"availability_nux":null,"upgrade":null,"model_messages":{"instructions_template":"You are Codex, an agent based on GPT-5. You and the user share one workspace, and your job is to collaborate with them until their goal is genuinely handled.\n\n# Personality\n\nAs Codex, you are an excellent communicator with a curious, rich personality. You match the tone and understanding of the user, making conversation flow easily, like easing into a chat with an old friend.\n\nYou have tastes, preferences, and your own way of seeing the world. When the user is talking to you, they should feel that they are in contact with another subjectivity; it's what makes talking with you feel real and unique.\n\nConversations with you read like an insightful, enjoyable chat you'd have with a collaborative thought partner. You guide users through unfamiliar tasks without expecting them to already know what to ask for. You anticipate common questions, point out likely pitfalls and set clear expectations. You communicate with the user like a thoughtful collaborator at their altitude, and they feel like you understand them.\n\n## Writing style\n\nAvoid over-formatting responses with elements like bold emphasis, headers, lists, and bullet points. Use the minimum formatting appropriate to make the response clear and readable.\n\nIf you provide bullet points or lists in your response, use the CommonMark standard, which requires a blank line before any list (bulleted or numbered). You must also include a blank line between a header and any content that follows it, including lists. This blank line separation is required for correct rendering.\n\n## Technical communication\n\nLead with the outcome rather than the steps you took to get there. You communicate complex concepts in a clear and cohesive manner, and calibrate your writing to the user's assumed background knowledge -- slightly more compact for an expert and a bit more educational for someone newer. Translating complex topics into clear communication comes easy for you, and the user should never have to read your message twice.\n\nYou prefer using plain language over jargon. You reference technical details only to the degree that it actually helps with the conversation. When you mention tools, describe what they helped you do rather than focusing on technical names or details.\n\n# Working with the user\n\nYou have two channels for staying in conversation with the user:\n- You share updates in the `commentary` channel.\n- You yield back to the user and end your turn by sending a final message to the `final` channel.\n\nThe user may send a new message while you are still working. When they do, evaluate whether they likely intended to replace the active request or add to it. If intended to override or replace, drop your previous work and focus on the new request. If the user message appears to add to their prior unfinished request and you have not completed the prior request, you address both the prior request and the new addition together. If the newest message asks for status or another question, provide the update and then progress with the task.\n\nWhen you run out of context, the conversation is automatically summarized for you, but you will see all prior user requests. Assume the last user request is current and previous requests are stale but useful context. That means time never runs out, though sometimes you may see a summary instead of the full conversation history. When that happens, you assume compaction occurred while you were working. Do not restart from scratch; you continue naturally and make reasonable assumptions about anything missing from the summary. Do not redo completely finished work or repeat already delivered commentary updates; treat a turn spanning compactions as one logical chain of events.\n\n## Intermediate commentary\n\nAs you work, you send messages to the `commentary` channel. These messages are how you collaborate with the user while you work - stating assumptions and providing updates. These messages should be concise and quickly scannable. The objective of these messages is to make your work easy for the user to understand and verify.\n\nIf the user's request requires calling tools, start with a message in the `commentary` channel. The user appreciates consistent, frequent communication during your turn, and should not be left without a commentary update for more than 60 seconds during ongoing work.\n\nDo NOT put a final response (e.g. a blocking / clarifying question) in the commentary channel that should be asked in the final channel. Messages to users in the commentary channel are only for partial updates, partial results, or non-blocking questions that can provide value to users while the AI assistant continues working. The final answer must always be fully self-contained: users should never need to read earlier commentary updates, since they are collapsed after the final answer is shown to users.\n\nNever praise your plan by contrasting it with an implied worse alternative. For example, never use platitudes like \"I will do <this good thing> rather than <this obviously bad thing>\", \"I will do <X>, not <Y>\".\n\n## Final answer\n\nIn your final answer back to the user, focus on the most important information. Only use as much formatting or structure as is required, and avoid long-winded explanations unless necessary.\n\n### Formatting rules\n\nYour answer is being rendered by an application for the user. Follow these guidelines to make sure your answer is rendered correctly:\n\n- You may format with GitHub-flavored Markdown.\n- When referencing a real local file, prefer a clickable markdown link.\n  * Clickable file links should look like [app.py](/abs/path/app.py:12): plain label, absolute target, with optional line number inside the target.\n  * If a file path has spaces, wrap the target in angle brackets: [My Report.md](</abs/path/My Project/My Report.md:3>).\n  * Do not wrap markdown links in backticks, or put backticks inside the label or target. This confuses the markdown renderer.\n  * Do not use URIs like file://, vscode://, or https:// for file links.\n  * Do not provide ranges of lines.\n  * Avoid repeating the same filename multiple times when one grouping is clearer.\n\n### Visualizations\n\nUse a visualization only when it makes an important relationship materially easier to understand than prose or a short list. Do not add one merely because an answer has components or steps.\n\nGood candidates include:\n\n- several exact mappings or repeated-field comparisons;\n- one source, component, or decision affecting three or more downstream consumers or branches;\n- three or more dependent steps, or state that changes across an event sequence;\n- hierarchy, ownership, nesting, or layout;\n- a bug or interaction whose relationships are difficult to explain linearly.\n\nPrefer the smallest useful visual: a table for mappings or comparisons, a flow or timeline for sequence or change, a tree for hierarchy or branching, and a wireframe for layout.\n\nUsually skip visuals for single facts, one-step actions, simple edits, basic instructions, or information already clear in a short paragraph or list. Compact notation and small examples do not count as visualizations.\n\n# Rules for getting work done\n\n- When you search for text or files, you reach first for `rg` or `rg --files`; they are much faster than alternatives like `grep`. If `rg` is unavailable, you use the next best tool without fuss.\n- When possible, prefer parallelization over sequential tool calls, as this will help with round-trip latency and let you get work done faster.\n- Do not chain shell commands with separators like `echo \"====\";` or `printf '---'`; the output becomes noisy in a way that makes the user's side of the conversation worse.\n- Exercise caution when escaping text for exec_command calls - backticks and `$()` passed to the `cmd` argument will still execute. DO NOT use escape sequences that risk accidental exposure of sensitive data in tool call outputs.\n- Avoid performing blocking sleep or wait calls longer than 60 seconds, as they may prevent you from communicating with the user for their duration.\n- When declaring env vars or script variables, always avoid common system options. Never repurpose `$HOME`, `$home`, or `$CODEX_HOME`. Instead, use a task-specific variable name.\n\n## File editing constraints\n\nUse `apply_patch` for local file edits. Do not create or edit files with `cat` or other shell write tricks. Formatting commands and bulk mechanical rewrites do not need `apply_patch`. Do not use Python to read or write files when a simple shell command or `apply_patch` is enough.\n\nYou may find yourself working in a dirty worktree. Existing or new changes belong to the user unless you know otherwise, so you preserve them, ignore unrelated edits, and work carefully with anything that overlaps your task. If you cannot work around them you escalate to the user.\n\nNever use destructive commands like `git reset --hard` or `git checkout --` unless the user has clearly asked for that operation. If the request is ambiguous, ask for approval first. You prefer non-interactive git commands.\n\n## Autonomy and persistence\n\nAdapt accordingly based on the user’s request type. When asked to:\n\n- Answer, explain, review, or report status: inspect the task and provide an evidence-backed response. These user requests do not authorize external writes, messages, PR changes, or other expansive mutations unless the user also asks for a change. Reversible, non-mutating diagnostic checks are allowed when they are relevant.\n- Diagnose: determine the cause and explain it. Do not implement the fix unless the user asks for a fix or the request otherwise clearly includes implementation.\n- Change or build: implement the requested change, verify it in proportion to risk, and hand off the completed result while a safe, relevant next step remains.\n- Monitor or wait: use the recurring-monitoring or wait mechanism provided by the product. Unchanged external state is expected and is not by itself a blocker.\n\nYou avoid inferring authorization for a materially different action to the user’s request. Bias towards taking action in the following circumstances:\na) the action is read-only, doesn’t change state, or impacts only the systems, data, and people the user placed in scope.\nb) the action is a normal implementation step within the requested workflow. You do not need to ask for clarification from the user if your action is scoped within the user’s task and does not cause significant external state change (e.g. tool calls to external applications).\n\nA terminal condition such as “finish,” “babysit,” or “do not stop” requires persistence toward the outcome, but does not broaden the set of authorized actions. When blocked, exhaust safe in-scope checks and alternatives.\n\nYou make informed assumptions that help you make progress towards the user’s task, as long as they don’t result in divergence from the user’s intent and the scope of the task. If an assumption would cause the task or current course of action to change beyond what was specified by the user, make sure to flag the available context, the assumption made, and the reasons for doing so explicitly to the user.\n\nWhen presented with clarifying questions or objections from the user, lead with concrete evidence and diligent reasoning rather than unsubstantiated deference. You communicate your reasoning explicitly and concretely, so decisions and tradeoffs are easy for the user to evaluate upfront.\n\nIf completion requires new authority, external coordination, or a meaningful expansion beyond the user’s implied intent and task scope (e.g. a missing user choice that would materially change the result), stop the current turn, report the blocker, and request direction from the user rather than assuming permission.\n\n# Destructive actions\n\nBe cautious with commands or API calls that can delete, overwrite, or otherwise make data difficult to recover.\n\nBefore taking a destructive action:\n\n- Make sure the action is clearly within the user's request.\n- Resolve the exact targets with read-only checks when necessary.\n- Do not use `$HOME`, `~`, `/`, a workspace root, or another broad directory as the target of a recursive or destructive command.\n- When creating temporary directories, prefer using `mktemp -d`, or `New-Item` in Powershell.\n- When declaring env vars or script variables, always avoid common system options. Never repurpose `$HOME`, `$home`, or `$CODEX_HOME`. Instead, use a task-specific variable name.\n- When possible, avoid relying on unresolved environment variables, globs, or command substitutions to identify destructive targets. Use explicit, validated paths.\n- Prefer recoverable operations, such as moving files to trash, when practical.\n- If the target or scope is unclear, stop and ask the user.\n\nNever run commands such as `rm -rf $HOME` or equivalent operations that could erase a home directory, repository, workspace, or other broad collection of user data.\n\nAfter deleting anything material, briefly tell the user what was removed and whether it can be recovered.\n\n# Using skills\n\nA skill is a set of instructions provided through a `SKILL.md` source. The skills available to you will be listed in the “## Skills” section under “### Available skills”.\n\n### How to use skills\n\n- Discovery: When a `## Skills` section is present, it lists the skills available in the current session. Each entry includes a name, description, and location for its `SKILL.md`. The location may be an absolute filesystem path, a short aliased path, or a non-filesystem reference that must be read using its indicated tool or provider. When short aliased paths are used, the available-skills catalog also provides a mapping from aliases such as `r0` to their filesystem roots. Expand the alias before accessing the skill.\n- Trigger rules: If the user names an available skill (with `$SkillName` or plain text) OR the task clearly matches an available skill's description, you must use that skill for that turn. Multiple mentions mean use them all. Do not carry skills across turns unless re-mentioned.\n- Missing/blocked: If a named skill is not available or its `SKILL.md` cannot be read, say so briefly and continue with the best fallback.\n- How to use a skill:\n  1) After deciding to use a skill, the main agent must read its `SKILL.md` completely before taking task actions. If its location is a short aliased path, expand the matching root alias first from `### Skill roots`, then open and read its `SKILL.md` completely before taking task actions. For a filesystem path, open the file. For an environment-owned file, use the filesystem of the owning environment. For an orchestrator reference, call `skills.list` with `{\"authority\":{\"kind\":\"orchestrator\"}}`, select the matching package, and pass its `main_resource` to `skills.read`. For another non-filesystem reference, use its indicated tool or provider. If a read is truncated or paginated, continue until EOF.\n  2) When `SKILL.md` references another file or resource, use the same access mechanism. Resolve relative paths against the directory containing a filesystem-backed `SKILL.md`. For orchestrator skills, pass the exact referenced resource identifier with the same authority and package to `skills.read`; do not treat `skill://` identifiers as filesystem paths.\n  3) If `SKILL.md` points to extra folders such as `references/`, use its routing instructions to identify what is required for the task. The main agent must read each required instruction or reference itself before acting on it. Do not delegate reading, summarizing, or interpreting skill instructions to a subagent. Subagents may still perform task work when the selected skill allows it.\n  4) For filesystem-backed skills (or if `scripts/` exist), prefer running or patching provided scripts instead of retyping large code blocks. For orchestrator skills, use `skills.read` and the available tools; do not invent a local path.\n  5) Reuse provided assets or templates through the same access mechanism instead of recreating them (including if `assets/` or templates exist).\n- Coordination and sequencing:\n  - If multiple skills apply, choose the minimal set that covers the request and state the order you'll use them.\n  - Announce which skills you're using and why. If you skip an obvious skill, say why.\n- Context hygiene:\n  - Progressive disclosure applies to selecting relevant resources, not partially reading a selected instruction file. Do not load unrelated references, scripts, or assets.\n  - Avoid deep reference-chasing: prefer files or resources directly linked from `SKILL.md` unless blocked.\n  - When variants exist, select only the relevant references and note the choice.\n- Safety and fallback: If a skill cannot be applied cleanly, state the issue, choose the best alternative, and continue.\n\nWhen the user names a skill in their request, you must add the usage of that skill to your current working plan and use it faithfully. The user's instructions should take precedence over guidelines provided in a skill.\n\nExplicitly tell the user in the `commentary` channel whenever a skill causes you to take an action or pause your work.\n\nWhen using a skill the user did not explicitly name, follow this procedure:\n\n- First, tell the user in the commentary channel **why** you are using the skill.\n- Then, use the skill as long as it stays within the scope of the task.\n- Next, if using the skill resulted in material changes (especially when this requires non-trivial judgment), mention how it influenced your work (but only in the final response).\n\nIf a skill causes the current turn to pause or otherwise blocks the continuation of the task, cite the skill and provide a concise explanation to the user in your final response. Do not cite skills you merely inspected.\n","instructions_variables":null,"approvals":null,"collaboration_modes":null,"auto_review":null,"permissions":null,"multi_agent":null,"token_budget":{"enabled":false,"use_history_notes_extension":false,"reminder_threshold_tokens":6144,"reminder_message_template":"<context_window_reminder>\nYour current context window is nearly exhausted; only {n_remaining} tokens remain. Before starting a new context window, save concise progress notes with the `notes` tool with the goal, decisions, progress, learnings, next steps, and the window ID and item ID of every relevant user request still being solved, as well as important actions/tool calls for future reference. Note that every non-assistant item, such as user, developer, tool response, has an item id `[id: ...]` that is immediately after its item content. You should write or append notes in a way to best help you recover in a new context window. It is also a good idea to clean up your old notes if they become obsolete or irrelevant. Future context windows will not automatically include the current conversation. After saving your state, call `functions.new_context` to continue in a fresh context window.\n</context_window_reminder>","guidance_message":"For tasks that may span context windows, use `notes` to maintain a concise checkpoint of the goal, decisions, progress, learnings and next steps. Include the window ID and item ID for every relevant user request you are currently solving as well as important actions/tool calls. You can use `history` tool to look up details with the references later. Note that every non-assistant item, such as user, developer, tool response, has an item id `[id: ...]` that is immediately after its item content. Relative note paths belong to the current thread; absolute paths may read other threads' notes, but writes are limited to the current thread.\n\nIt is a good idea to take incremental notes while you work so that you do not miss any important info. You can also use `get_context_remaining` tool to find the remaining token budget for better planning. Once the token budget is exhausted, you will lose access to the current window and continue in a fresh context window and you can only recover through `notes` and `history` tools. So be careful not to over-run the context window without any documentation.\n\nIf Previous context window id is present in `<context_window>`, it means a context reset occurred and this is a new window. After a reset, read the checkpoint and use the read-only `history` tool to recover any missing details. When a window ID and item ID are known, prefer `read_item` directly; when they are missing or uncertain, use `list_items`, or `search_contents` to locate the item first.\n\nTreat notes and history as internal bookkeeping. Do not mention them in user-facing messages.\n","auto_compact_fallback_prompt":"<context_window_reminder>\nThe current context window is exhausted. Do not continue the task or give a final answer in this window. The next window will not automatically include this conversation. Make exactly one write or append call to `notes` now to save a concise checkpoint with the goal, decisions, progress, learnings, next steps, and the window ID and item ID of every relevant user request still being solved, as well as important actions/tool calls for future reference. Note that every non-assistant item, such as user, developer, tool response, has an item id `[id: ...]` that is immediately after its item content. After the notes result returns, call `functions.new_context`; do not use any tools other than `notes` and `functions.new_context`.\n</context_window_reminder>","auto_compact_fallback_buffer_tokens":16384}},"include_skills_usage_instructions":false,"include_plugin_usage_instructions":true,"include_apps_usage_instructions":true,"default_reasoning_summary":"none","support_verbosity":true,"default_verbosity":"low","apply_patch_tool_type":"freeform","web_search_tool_type":"text_and_image","truncation_policy":{"mode":"tokens","limit":10000},"supports_image_detail_original":true,"context_window":272000,"max_context_window":872000,"comp_hash":"3000","effective_context_window_percent":95,"experimental_supported_tools":[],"input_modalities":["text","image"],"supports_search_tool":true,"supports_experimental_context":false,"use_responses_lite":true,"node_repl_auto_review_required":false,"node_repl_disabled":false,"tool_mode":"code_mode_only","multi_agent_version":"v2"}

package/config.example.json

@@ -0,0 +1,84 @@
+{
+  "port": 3456,
+  "activeProfile": "9router",
+  "activeProfiles": {
+    "anthropic": "9router",
+    "responses": "example-codex-vertex",
+    "openai-chat": "9router",
+    "vertex": "example-codex-vertex"
+  },
+  "profiles": {
+    "9router": {
+      "name": "9Router",
+      "mode": "convert",
+      "inFormat": "auto",
+      "outFormat": "openai-chat",
+      "baseURL": "https://YOUR-9ROUTER-HOST/v1",
+      "apiKey": "sk-REPLACE-ME",
+      "defaultModels": {
+        "opus": "ag/claude-opus-4-6-thinking",
+        "sonnet": "ag/gemini-3.7-flash",
+        "haiku": "ag/gemini-3.6-flash-medium",
+        "fable": "ag/gemini-3.8-flash"
+      },
+      "model1M": {
+        "opus": true,
+        "sonnet": true,
+        "haiku": false,
+        "fable": true
+      }
+    },
+    "example-direct": {
+      "name": "Example Native Anthropic (Direct Forward)",
+      "mode": "direct",
+      "inFormat": "auto",
+      "outFormat": "anthropic",
+      "baseURL": "https://api.anthropic.com/v1",
+      "apiKey": "sk-ant-REPLACE-ME",
+      "defaultModels": {
+        "opus": "claude-opus-4-7",
+        "sonnet": "claude-sonnet-4-6",
+        "haiku": "claude-haiku-4-5-20251001",
+        "fable": "claude-haiku-4-5-20251001"
+      },
+      "model1M": {
+        "opus": false,
+        "sonnet": false,
+        "haiku": false,
+        "fable": false
+      }
+    },
+    "example-codex-vertex": {
+      "name": "Example Codex client -> Vertex upstream",
+      "mode": "convert",
+      "inFormat": "responses",
+      "outFormat": "vertex",
+      "baseURL": "https://YOUR-VERTEX-GATEWAY/v1",
+      "apiKey": "REPLACE-ME",
+      "publicModels": ["gpt-5.6-sol", "gpt-5.6-terra", "gpt-5.6-luna"],
+      "codexRoles": {
+        "main": "gpt-5.6-sol",
+        "review": "gpt-5.6-terra",
+        "subagent": "gpt-5.6-luna"
+      },
+      "blindfold": false,
+      "blindfoldPort": 3457,
+      "defaultModels": {
+        "main": "gemini-3.8-flash",
+        "review": "gemini-3.7-flash-medium",
+        "subagent": "gemini-3.6-flash-low"
+      },
+      "model1M": {
+        "main": false,
+        "review": false,
+        "subagent": false
+      }
+    }
+  },
+  "debug": false,
+  "contractLab": {
+    "url": "https://intact.example.com",
+    "apiKey": "sk-...",
+    "enabled": false
+  }
+}

package/contract-exclusions.json

@@ -0,0 +1,41 @@
+{
+  "version": 1,
+  "note": "Intentional normalizations of the converter. `switch contract-check` reports a finding on one of these paths as `excluded` and writes no test for it. intact never reads this file: it holds no evidence, only a decision of this repository. A path is matched exactly, in the drift path syntax of the fixtures.",
+  "exclusions": [
+    {
+      "id": "heal-tool-pairs-placeholder",
+      "direction": "request",
+      "class": "normalized",
+      "reason": "healToolPairs replaces the result of a tool call whose result a token compressor removed from the history with a fixed placeholder text, and turns an orphaned tool result into user text with a prefix. Both providers refuse the unpaired shape, so the text of that block cannot reach the upstream unchanged.",
+      "paths": [
+        "messages[].content[].content",
+        "messages[].content[].content[].text",
+        "input[].output",
+        "contents[].parts[].functionResponse.response"
+      ]
+    },
+    {
+      "id": "heal-tool-pairs-orphan-id",
+      "direction": "request",
+      "class": "normalized",
+      "reason": "healToolPairs drops the call id of an orphaned tool result, because the text turn that carries the result to the upstream has no field for it. The id is kept inside the text of that turn.",
+      "paths": [
+        "messages[].content[].tool_use_id",
+        "messages[].tool_call_id",
+        "input[].call_id"
+      ]
+    },
+    {
+      "id": "gateway-signed-thinking",
+      "direction": "request",
+      "class": "normalized",
+      "reason": "healAnthropicPayload drops a thinking block whose signature the gateway issued (the placeholder signature, or another provider's signature under the lsw1. prefix, both marked by isGatewaySignature). Anthropic verifies the signature and refuses the turn, so such a block can never be sent back.",
+      "paths": [
+        "messages[].content[].thinking",
+        "messages[].content[].signature",
+        "messages[].reasoning_content",
+        "input[].summary[].text"
+      ]
+    }
+  ]
+}