[Feature Request] GLM Coding Plan: Add Support for New Agentic Platforms β Buzz (Block/Jack Dorsey) & Odysseus
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 22
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Feature Request: GLM Coding Plan Support for New Agentic Platforms
π Summary
Add official support for two emerging open-source agentic platforms to the GLM Coding Plan:
- Buzz β by Block (Jack Dorsey's company) β https://github.com/block/buzz
- Odysseus β by odysseus-dev β https://github.com/odysseus-dev/odysseus
Enable GLM Coding Plan subscribers to use these platforms with their existing plan credentials, similar to current support for Cursor, Windsurf, ZCode, OpenCode, etc.
π― Problem Description
Current State
GLM Coding Plan currently supports a range of IDEs and agentic platforms:
- β ZCode (official)
- β Cursor
- β Windsurf
- β OpenCode
- β VS Code extensions
- And others...
Missing: Buzz & Odysseus β two new, rapidly growing open-source agentic platforms that the community wants to use with their GLM Coding Plan subscription.
User Request
"It would be cool if you would support Jack Dorsey's Buzz and then Odysseus. Both on github."
β Franta VΔdomΓ½ svobody/Ε tΔstΓΔko (Discord)
Why This Matters
| Platform | Why Users Want It |
|---|---|
| Buzz | Backed by Block (Jack Dorsey/Square), open-source, growing ecosystem, alternative to proprietary agent tools |
| Odysseus | Community-driven, flexible architecture, gaining traction in developer circles |
User Benefits:
- More choice in tooling while using existing GLM Coding Plan subscription
- Avoid being locked into single vendor's IDE
- Leverage GLM's capabilities across different agent architectures
- Support open-source alternatives to commercial products
π Platform Details
1. Buzz (by Block)
Repository: https://github.com/block/buzz
About:
- Developed by Block, Inc. (formerly Square, led by Jack Dorsey)
- Open-source agentic development platform
- Focus on autonomous coding agents
- Part of Block's open-source initiative
Why Add Buzz:
- High-profile backing (Jack Dorsey/Block brand)
- Active development and growing community
- Enterprise credibility + open-source flexibility
- Natural fit for GLM Coding Plan users who want alternatives to Cursor/Windsurf
2. Odysseus
Repository: https://github.com/odysseus-dev/odysseus
About:
- Community-developed agentic platform
- Flexible, modular architecture
- Designed for extensibility and customization
- Growing adoption in developer communities
Why Add Odysseus:
- Community-driven development (responsive to user needs)
- Lightweight alternative to heavier platforms
- Strong technical architecture for agent workflows
- Popular with power users who want control
β Proposed Solution
Integration Approach
Similar to existing platform integrations:
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ GLM Coding Plan Platform Support ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€β ββ Currently Supported: ββ βββββββββ ββββββββ ββββββββββ βββββββββββ ββββββββββββ ββ βZCode β βCursorβ βWindsurfβ βOpenCode β βVS Code β ββ βββββββββ ββββββββ ββββββββββ βββββββββββ ββββββββββββ ββ ββ REQUESTED ADDITIONS: ββ βββββββββββββ βββββββββββββ ββ β Buzz β β Odysseus β β NEW ββ β (Block) β β(Community)β ββ βββββββββββββ βββββββββββββ ββ ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ```
### What "Support" Means
For each platform, GLM Coding Plan integration should provide:
| Feature | Description |
|---------|-------------|
| **API Authentication** | Use GLM Coding Plan OAuth/API key with the platform |
| **Model Access** | GLM models (GLM-5.3, GLM-5-Turbo, etc.) available as model options |
| **Quota Integration** | Usage counts against user's Coding Plan quota (not separate billing) |
| **Rate Limits** | Apply appropriate rate limits per plan tier |
| **Documentation** | Setup guide for connecting platform to GLM Coding Plan |
### Technical Requirements
```yaml
# For each platform, provide:
Platform: Buzz
Repository: https://github.com/block/buzz
Auth Method: OAuth 2.0 / API Key
Config Location: ~/.buzz/config.json or equivalent
Model Endpoint: Compatible with OpenAI API format?
Notes: Verify API compatibility layer
Platform: Odysseus
Repository: https://github.com/odysseus-dev/odysseus
Auth Method: API Key / OAuth
Config Location: ~/.odysseus/config or equivalent
Model Endpoint: Compatible with OpenAI API format?
Notes: Check documentation for LLM provider setup
π Implementation Checklist
Phase 1: Assessment (1-2 weeks)
- Review Buzz codebase for API/LLM provider integration points
- Review Odysseus codebase for API/LLM provider integration points
- Determine authentication mechanism each platform expects
- Assess compatibility with existing GLM API endpoints
- Identify any custom work needed (adapters, plugins, config)
Phase 2: Development (2-4 weeks)
- Build authentication bridge for Buzz β GLM Coding Plan
- Build authentication bridge for Odysseus β GLM Coding Plan
- Create configuration templates for each platform
- Test model access and response quality
- Implement quota tracking for usage on these platforms
Phase 3: Documentation & Launch (1 week)
- Write setup guides for Buzz + GLM Coding Plan
- Write setup guides for Odysseus + GLM Coding Plan
- Add to supported platforms list on website/docs
- Announce to community (Discord, social media)
- Gather initial feedback from testers
π― Success Metrics
| Metric | Target |
|---|---|
| Platform integration completed | Both Buzz & Odysseus working within 6 weeks |
| User adoption | >100 active users on each platform within 2 months |
| Support ticket volume | <10% increase in platform-specific issues |
| User satisfaction | >4.0/5.0 rating from early adopters |
π‘ Additional Context
- Affected Product: GLM Coding Plan (subscription service)
- Primary Requester: Franta VΔdomΓ½ svobody/Ε tΔstΓΔko (Discord)
- Discord Thread: https://discord.com/channels/1346756824233148527/1533514787882008606
- Platforms Requested:
- Strategic Value: Expands GLM ecosystem, supports open-source tools, reduces vendor lock-in
β Questions for Team
- Are there any existing plans to support these platforms?
- What is the typical timeline for adding new platform support?
- Are there specific technical requirements or APIs these platforms must implement to be compatible?
- Would community contributors be able to help build/maintain these integrations?
- Is there a formal process for requesting new platform support that we should direct users to?
Submitted by:
Regards,
Roman (Discord: bignavi_x)
- Z.ai Volunteer Ambassador
- Tech resources channel: https://t.me/VibeCodePrompterSystem
- Tech Blog: http://claw.rommark.dev/blog
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up β it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin by reviewing the repository's existing platform integrations, then inspect the linked Buzz and Odysseus repositories for provider, authentication, and configuration entry points. Confirm whether Coding Plan credentials, model access, quota handling, and rate limits are supported before defining the integration scope. Done means both platforms have a concrete compatibility assessment and documented implementation requirements.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100