Ox Alpha Same-Session Typecheck Audit and Custom-Instruction Writeback

One-sentence takeaway

When Ox Alpha continues to report errors after repeated typechecks in OpenCode, ask it to audit the errors in the same session, then write verified repair principles back into custom instructions to create a project-specific feedback loop.

Use cases

• Suitable tasks: TypeScript/frontend type-error review and codifying project-level coding conventions.

• Unsuitable tasks: Writing model inferences into global rules without human confirmation, or treating one successful repair as a guarantee of type safety.

• Applicable model version: Ox Alpha; no version snapshot is provided.

• Applicable clients, agents, or APIs: OpenCode; the comment explicitly mentions custom instructions.

• Recommended reasoning levels and parameters: Not disclosed; keep the original reasoning level fixed and record error batches, repair count, and final tests.

Ready-to-use content

The original post does not publish the full custom instructions it used. The following is a reusable configuration workflow, not the original prompt:

1. Run typecheck in the same OpenCode session and save the complete error output, file paths, and line numbers.
2. Ask Ox Alpha to first classify the errors as “root cause / cascading error / type-declaration-only issue”; do not immediately modify every file.
3. Propose the smallest repair for each error category and explain which runtime behavior will not change; modify in batches and rerun typecheck after each batch.
4. Write only general principles that have been verified by typecheck, tests, or a build into the project's custom instructions, for example:
   - Before changing types, find the real callers and export boundaries;
   - Do not use `any` to conceal unresolved type conflicts;
   - Rerun the original typecheck command after every change.
5. Start a clean session and execute a small task to confirm that the new instructions do not cause over-editing or unrelated refactoring.

Original experience and boundaries

The author says that Ox Alpha encountered 15–25 errors during typechecking. After asking the model to audit the errors in the same session and write the repairs into OpenCode custom instructions, the author said it “works for now.” This is a personal experience; no repository, error log, instruction content, or before-and-after comparison data was published.

Reuse notes

• Write back verified project rules, not the model's temporary guess about a particular error.

• Preserve the chain of “original errors → repair diff → recheck” to avoid mistaking disappearing errors for a resolved problem.

• Manage global instructions, repository instructions, and one-off prompts separately so they can be rolled back.