Companion to: existing gist Transport Tradeoffs & iOS WebSocket Design Sketch
Date: 2026-03-11
The agentic-coach-prototype-v2 defines a parity contract — a WebSocket protocol that an iOS client speaks to connect to a coaching session. This documents what that contract requires vs what the current Node.js backend (CoachEx-Backend, /coach WebSocket) actually implements.
| #!/usr/bin/env bash | |
| # Claude Code Version Manager | |
| # | |
| # Download, manage, and install specific versions of Claude Code. | |
| # Useful when the latest release has issues and you need to pin or rollback. | |
| # | |
| # Binaries are downloaded to ~/.claude/downloads/ and installed to ~/.local/bin/claude. | |
| # Each download is SHA-256 verified against the official manifest. | |
| # | |
| # Usage: |
So I have one question Milan Novakovic, I am currently looking into how to organise things both internally (for employees) and externally for Memgraph users. I will share my thoughts about what I am thinking.
We have a mgconsole CLI tool, and I have decided to have that as an mgconsole skill. So Memgraph provided an official mgconsole skill that describes how mgconsole can be used.
But mgconsole also changes with time, so as the version changes, the skill should potentially change, giving the LLM the latest version, assuming that next to the mgconsole you also want say Mage skill that is a set of algorithms you would want to use. Let's say we have third skill like memgraph helm for k8s, but you don't want that since you are not using k8s.