[Feature] Add PI Agent to the GLM Coding Plan's officially supported tools list

Summary

Request: add PI Agent to the list of officially supported tools for the GLM Coding Plan, alongside Claude Code, Cline, OpenCode, Cursor, OpenWiki, etc.

PI Agent is an emerging agent-based coding tool that fits the same workflow profile as the tools already on the supported list. Today it is not listed at https://docs.z.ai/devpack/tool/others, so using Coding Plan quota with it technically falls outside the plan's ToS — forcing users to either fall back to the pay-per-use API (/paas/v4) or skip GLM entirely for that workflow.

Why it's a natural fit for the Coding Plan

• Same audience. PI Agent's users are exactly the Coding Plan's users — developers running coding agents on a codebase, doing long-running, high-token work.
• OpenAI-compatible endpoint pattern. Like the other supported tools (Cline, OpenCode, OpenWiki, etc.), PI Agent can be pointed at https://api.z.ai/api/coding/paas/v4 using the standard openai-compatible provider. No protocol work on Z.AI's side — it's a config one-liner.
• High-token, agentic workload. The whole value prop of the Coding Plan is sustained agentic usage; PI Agent produces exactly that kind of load.
• Ecosystem synergy. Each additional tool added to the supported list strengthens the GLM ecosystem around coding agents. Users who already use PI Agent alongside Claude Code / Cline / OpenCode get a consistent billing path for all of them.

What "supporting" it would mean

In practice, the same minimal change as #120 (OpenWiki): list PI Agent under "Coding Agent Tool" at https://docs.z.ai/devpack/tool/others so its usage is covered by the Coding Plan ToS. Endpoint configuration matches the existing openai-compatible tools:

PROVIDER=openai-compatible
OPENAI_COMPATIBLE_BASE_URL=https://api.z.ai/api/coding/paas/v4
MODEL_ID=glm-4.6

Current blocker

Today, PI Agent is not on the supported-tools list, so using Coding Plan quota with it technically violates: "users may not use their subscription benefits for tools or scenarios outside of this scope." Users are forced to either pay per-token on /paas/v4 or drop GLM for that part of their workflow — neither is a good outcome for Z.AI retention.

Related

• #120 — same class of request (adding OpenWiki to the supported tools list).

Notes

• Project URL / repo: (to be confirmed — please reply with the official PI Agent GitHub repo or homepage and I'll update this issue.)

Regards,
Roman
http://www.rommark.dev
VIbe Coders Telegram Channel: https://t.me/VibeCodePrompterSystem

Start with the documentation page at https://docs.z.ai/devpack/tool/others and compare this request with #120, which covers adding OpenWiki. Confirm PI Agent's official GitHub repository or homepage, then update the Coding Agent Tool list so PI Agent is included and verify the endpoint/configuration details remain consistent.