InteJer v0.1.0-beta.6

InteJer Agent

A new agent in the picker. Press Tab and choose intejer-agent.

Most coding agents hand your whole task to a single model: the same context window that plans the work also executes it. On a job that runs from schematic to firmware to broker to dashboard, that model runs out of room and starts guessing. InteJer Agent splits the two jobs.

• A frontier model does the thinking. Claude Sonnet 5 reads the full session transcript — everything the agent has seen and done, not a summary — and weighs in at three moments: before work starts (plan), when the agent gets stuck (stuck), and before it calls the job done (verify).
• A 1M-token model does the work. GLM 5.2 does the reading, editing and running, so your KiCad schematic, the firmware that drives it, the MQTT topic map and the dashboard that renders the telemetry all stay in context at the same time.

You get frontier-model judgment on the decisions that actually matter, and a long-context model everywhere else. That is the whole point: a single general-purpose model has to choose between thinking hard and holding your entire stack in its head. InteJer Agent doesn't.

Details

• The advisor lives server-side. Prompts and model routing sit in the InteJer gateway, so the agent gets better without you reinstalling anything.
• It never blocks your run. Offline, signed out, or over your allowance — the executor just proceeds on its own judgment. A consult that fails is a consult you don't get, not a run that dies.
• Consults are metered as the InteJer Agent SKU and appear on your billing page. Team plans include 150 runs per seat per month.
• Scoped to intejer-agent only. The build, plan and pcb-engineer agents are unchanged and never see the advisor.

Install

Windows 10/11 (64-bit). This build is unsigned — SmartScreen will warn on first launch. Choose More info → Run anyway.