About this template
Shell on, model wired, start editing
If you want a coding agent running GLM-5.2 without losing an evening to provider config, this box is DeepAgents Code (dcode) already pointed at GLM-5.2 through OpenRouter, with the shell tool enabled.
You bring one key. That is the whole setup.
Why GLM-5.2 on OpenRouter
One account, one key, one model id — and the model id is the part everybody gets wrong.
Point a coding agent at the wrong route and you get a confident agent that cannot call a tool, or a 404 you debug instead of shipping. This template ships that route already set as the default model path. The first thing you do on the box is code, not configure.
The first five minutes
- Fork the template.
- Set the key in the shell:
export OPENROUTER_API_KEY=...
- Start
dcodeand give it a real task: list the repo, edit a file, run the test command.
Read, then edit, then shell — without re-teaching the model routing.
What lands in your fork
- DeepAgents Code (
dcode) agent config - GLM-5.2 over OpenRouter as the default model path
- The shell tool enabled, so the agent can run what it just wrote
What you bring (BYOK)
One OPENROUTER_API_KEY. It covers GLM-5.2.
No keys are in the snapshot — the template ships scrubbed, and the key you export lives on your microVM. OpenRouter bills your tokens to you.
Who this is for
- You want an open-weight coding agent, not a frontier-only workflow
- You are tired of re-wiring OpenRouter model ids every session
- You need shell, not chat-only autocomplete
Who this is not for
- Claude-subscription-only workflows with no OpenRouter account
- Anyone who needs a specific non-
dcodeharness UI - Managed enterprise VPC setups where BYOK is off the table
Honest limits
This is dcode, not a general chat UI.
GLM-5.2 is the default path here, not a lock — dcode is model-agnostic underneath, and repointing it at another OpenRouter model is on you. Nothing here fine-tunes GLM-5.2 or stacks prompts on top of it either. The value is narrow and real: the routing is done and the shell is on.
Fork it. Export the key. Make it edit something and run it. Your first jurniti purchase carries a 30-day money-back guarantee.