diegosouzapw/OmniRoute · error · Error
Not yet implemented — Trae viability under investigation…
Error message
Not yet implemented — Trae viability under investigation. See plan 11 §5.
What it means
Deliberate placeholder throw in TraeHandler.intercept: the Trae agent's MITM interception is not implemented yet (viability under investigation, plan 11 §5), so any intercepted Trae request is rejected with this structured sentinel. Means the request reached the proxy for an agent whose upstream API surface is unconfirmed — the UI correspondingly shows viability 'investigating' with no Setup button. Not a runtime fault.
Solutions
- Do not route Trae traffic through the MITM proxy until the handler ships
- Track plan 11 §5 for the viability decision and concrete implementation
- Return the unsupported-agent error to the caller as-is
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at src/mitm/handlers/trae.ts:22 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of diegosouzapw/OmniRoute@a179ffed5b (2026-08-25).
Data as JSON: /api/errors/68ded2f1601e4114.
Report an issue: GitHub.
Appendix: source
Thrown at src/mitm/handlers/trae.ts:22
* D14: Trae viability is still under investigation (see plan 11 §5). The
* concrete handler will be implemented once we confirm the upstream API
* surface. Until then, calling `intercept()` throws a structured error and
* the UI exposes the agent as `viability: "investigating"` (no Setup button).
*/
import type { IncomingMessage, ServerResponse } from "node:http";
import type { AgentId } from "../types";
import { MitmHandlerBase } from "./base";
export class TraeHandler extends MitmHandlerBase {
readonly agentId: AgentId = "trae";
async intercept(
_req: IncomingMessage,
_res: ServerResponse,
_body: Buffer,
_mappedModel: string,
): Promise<void> {
throw new Error("Not yet implemented — Trae viability under investigation. See plan 11 §5.");
}
}
View on GitHub (pinned to a179ffed5b)