plans
🚀 Power Upgrades
High-leverage Moincraft capability upgrades: OpenRouter features, streaming, memory, vision, routing, and skill growth.
These are capability opportunities, not current-state guarantees.
Highest-leverage upgrades#
| Theme | Opportunity | Why it matters |
|---|---|---|
| Embeddings | Native OpenRouter embeddings | Simpler semantic RAG with one provider boundary. |
| Streaming | SSE/token streaming | Lower-latency UX and live dashboard feedback. |
| Structured outputs | JSON-schema command responses | Fewer hallucinated commands and retry loops. |
| Routing | Provider/fallback policies | Better cost/speed tuning per agent. |
| Memory | Persistent vector memory | Facts survive restarts and accumulate. |
| Vision | Viewer-backed screenshots | Reuse existing render surface for multimodal decisions. |
| Cost tracking | Per-bot usage visibility | Budget-aware swarm operation. |
| Skill learning | Persist successful generated actions | Bots improve from successful code. |
Best-practice reminders#
- keep context windows tight;
- separate cheap chat models from smarter code models;
- rate-limit self-prompt loops;
- keep swarm profile names unique;
- treat viewer and server tuning as system-capacity work, not prompt work.
Rule#
A power-up idea becomes reference documentation only after implementation and verification land in canonical runtime pages.
Sources: wiki/content/docs/power.md, moincraft/docs/plans/roadmap-vision.md.