[v0.2.0] Call for proposals

This is the umbrella tracking issue for the AgentCube v0.2.0 release.

AgentCube has reached its first set of working components — Workload Manager (control plane), Router (data plane), PicoD (runtime), the AgentRuntime and CodeInterpreter CRDs, a Redis/ValKey-backed session store, mTLS between internal components, plus a Python SDK, CLI, and integrations (LangChain, Dify, MCP). The goal of v0.2.0 is to harden these foundations, close gaps in the existing features, and improve the developer/operator experience.

This issue is open to the whole community. Anyone is welcome to propose new features, enhancements, cleanups, docs, or test improvements. Comment below with your proposal , and we'll triage it into the checklist and create a dedicated sub-issue.

📋 Candidate Work Items

Checkboxes are checked as the work merges. Items are candidates until triaged — feel free to vote 👍 or propose changes in the comments.

Feautres

• TBD

Security & Auth

• Automate Alpine base image updates with Dependabot. (@ranxi2001, #422)
  • Some Dockerfiles in this repository use Alpine as the runtime base image, for example docker/Dockerfile and docker/Dockerfile.router. These base image versions can become outdated over time, which may increase security maintenance burden and leave known vulnerabilities unpatched.
  • We should introduce an automated mechanism to keep Docker base images up to date, especially Alpine images.
  • A possible solution is to configure Dependabot for Docker image updates, similar to Karmada’s approach.

Cleanup/Testing/CI

• Pin GitHub Actions Ubuntu runners. (@ranxi2001, #423)
• Update Golang to v1.26.4 (@ranxi2001, #391)
• Remove unused agentd component. (@ranxi2001, #403)
• Enable CI workflow in fork repos. (@ranxi2001, #414)
• Introduce proposal template. (@ranxi2001, #415)
• Fix failing chart workflow. (@ranxi2001, #416)
• Performance improvement for multi-arch images.(@ranxi2001, #420)

How to Propose Something

Just comment on this issue and tell us, in your own words:

• What you'd like to see in v0.2.0 (a feature, enhancement, cleanup, doc, test, or fix), and
• Why it matters (the problem it solves or the value it adds).

If you're willing to work on it, let us know. Maintainers will triage proposals into the checklist above and, where appropriate, create dedicated sub-issues linked back here.

No single file or test is named; start by reading the candidate work-item checklist and the existing v0.2.0 comments. A proposal is done when its value and scope are explained, maintainers triage it into the checklist, and an appropriate dedicated sub-issue is created.