rickub
bots-garden/mini-mepublic Fork
⑂ cb42032
Branches
feature/agents-file feature/ask-agent-hooks feature/ask-cli feature/declared-tools feature/display-called-hooks feature/fetch-build-in feature/genkit-v1.13.1 feature/github-mcp-in-sbx feature/go-1.27.3 feature/hooks feature/improve-init feature/interactive-prompt feature/last-question feature/llmman-provider feature/log-errors feature/lsp-builtin feature/mcp-gateway-session feature/mcp-support feature/memory-search feature/mini-mes feature/mm-init feature/open-terminal feature/prompt-flag feature/response-request feature/resume-acp feature/sbx-template-kit feature/search-in-doc feature/selectors feature/skill-discovery feature/structured-output feature/system-one feature/talk-to-another-mm feature/tasks-builtin feature/try-again feature/unload-model feature/wasm-custom-tools feature/yolo feature/zed-skill-selector fix/generation-timeout fix/plan-mode fix/too-long-completion fix/tool-order fix/word-wrap improve-mem-usage main thinking
Tags
v0.0.0 v0.0.1 v0.0.2 v0.0.3 v0.0.4 v0.1.0 v0.1.1 v0.1.2 v0.1.3 v0.1.4 v0.1.5 v0.1.6 v0.1.7 v0.1.8 v0.1.9 v0.2.0 v0.2.1 v0.2.2 v0.2.3 v0.2.4 v0.2.5 v0.2.6 v0.3.0 v0.4.0 v0.5.0 v0.6.0 v0.7.0 v0.8.0 v0.9.0 v1.0.0 View all branches → View all tags →
Commits
⬇ Clone ▾
git clone https://git.rickub.com/bots-garden/mini-me.git
git clone ssh://git@rickub.com/bots-garden/mini-me.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

Download ZIP

🛟 Updated.

k33g committed 2026-09-30T08:39:02+02:00 Browse files
cb42032 parent: 050d1d0
added .tickets/issues/0054-how-to-force-the-json-output.yaml +13 -0
new file mode 100644
@@ -0,0 +1,13 @@
1+# Managed by IssueSpec. Hand edits are welcome; keep the schema valid.
2+id: 54
3+title: How to force the JSON output?
4+state: open
5+author:
6+ name: k33g
7+ email: ph.charriere@gmail.com
8+createdAt: 2026-09-30T06:35:54.771Z
9+updatedAt: 2026-09-30T06:35:54.771Z
10+labels: []
11+body: ""
12+tasks: []
13+comments: []
new file mode 100644
@@ -0,0 +1,13 @@
1+# Managed by IssueSpec. Hand edits are welcome; keep the schema valid.
2+id: 54
3+title: How to force the JSON output?
4+state: open
5+author:
6+ name: k33g
7+ email: ph.charriere@gmail.com
8+createdAt: 2026-09-30T06:35:54.771Z
9+updatedAt: 2026-09-30T06:35:54.771Z
10+labels: []
11+body: ""
12+tasks: []
13+comments: []
added .tickets/issues/0055-how-to-query-another-model-and-force-the-json-ou.yaml +17 -0
new file mode 100644
@@ -0,0 +1,17 @@
1+# Managed by IssueSpec. Hand edits are welcome; keep the schema valid.
2+id: 55
3+title: How to query another model and force the JSON output (then use the result)
4+state: open
5+author:
6+ name: k33g
7+ email: ph.charriere@gmail.com
8+createdAt: 2026-09-30T06:37:48.693Z
9+updatedAt: 2026-09-30T06:38:40.601Z
10+labels: []
11+related:
12+ - 54
13+ - 52
14+ - 51
15+body: ""
16+tasks: []
17+comments: []
new file mode 100644
@@ -0,0 +1,17 @@
1+# Managed by IssueSpec. Hand edits are welcome; keep the schema valid.
2+id: 55
3+title: How to query another model and force the JSON output (then use the result)
4+state: open
5+author:
6+ name: k33g
7+ email: ph.charriere@gmail.com
8+createdAt: 2026-09-30T06:37:48.693Z
9+updatedAt: 2026-09-30T06:38:40.601Z
10+labels: []
11+related:
12+ - 54
13+ - 52
14+ - 51
15+body: ""
16+tasks: []
17+comments: []
modified INSTALL.MACOS.md +1 -62
@@ -2,7 +2,7 @@
22
33 ```bash
44 # download the binary release in https://rickub.com/bots-garden/mini-me/releases
5-VERSION=0.2.1
5+VERSION=0.2.4
66 curl -fsSLO "https://rickub.com/bots-garden/mini-me/releases/download/v${VERSION}/mm-${VERSION}-darwin-arm64"
77 chmod +x ./mm-${VERSION}-darwin-arm64
88 xattr -cr ./mm-${VERSION}-darwin-arm64
@@ -10,64 +10,3 @@ sudo rm -f /usr/local/bin/mm
1010 sudo cp ./mm-${VERSION}-darwin-arm64 /usr/local/bin/mm
1111 ```
1212
13-## Use `mm` in a Docker Sandbox (the two kits)
14-
15-Instead of installing the binary, `mm` can run inside a [Docker Sandbox](https://docs.docker.com/ai/sandboxes/): every command the model runs and every file it edits then happens in a container, on your mounted project. Two kits are published on Docker Hub at mm's version; each one brings the `k33g/mm-sandbox` image with `mm` in it, so nothing is built on your Mac.
16-
17-| Kit | For |
18-|---|---|
19-| `k33g/mm-tui:0.2.1` | the window mode (`mm -tui`) in your terminal |
20-| `k33g/mm-acp:0.2.1` | an editor that speaks the Agent Client Protocol (Zed, …) |
21-
22-You need Docker Desktop with the `sbx` command, and your model server (Docker Model Runner or llama-server) running on the Mac. Inside the sandbox, `localhost` is the sandbox itself: `agent.dmr.yaml` already falls back to `host.docker.internal`, which reaches the Mac.
23-
24-### Window mode: `mm-tui`
25-
26-From the project you want `mm` to work on:
27-
28-```bash
29-cd /path/to/your/project
30-sbx kit inspect k33g/mm-tui:0.2.1 # optional: what the kit declares
31-sbx run k33g/mm-tui:0.2.1 . -- agent.dmr.yaml
32-```
33-
34-What follows `--` is `mm`'s own command line (here the configuration file, relative to the project). `sbx ls` lists the sandboxes; `sbx run --name <name>` re-attaches to one.
35-
36-### From an editor: `mm-acp`
37-
38-Create the sandbox once, from the project the editor will open, with the configuration file baked in:
39-
40-```bash
41-cd /path/to/your/project
42-sbx create --name mm-acp k33g/mm-acp:0.2.1 . --kit-arg config=agent.dmr.yaml
43-```
44-
45-Then register it in Zed's `settings.json`:
46-
47-```json
48-{
49- "agent_servers": {
50- "mini-me (sandbox)": {
51- "type": "custom",
52- "command": "sbx",
53- "args": ["exec", "-i", "mm-acp", "mm", "-acp"]
54- }
55- }
56-}
57-```
58-
59-If Zed cannot find `sbx`, put the absolute path given by `which sbx` in `"command"`. One sandbox per project: give each one its own `--name` and its own entry in Zed. `sbx rm mm-acp` removes a sandbox; your project directory is not touched.
60-
61-### The v3 kits
62-
63-The same two kits also exist for the kit specification v3, in `docker-sbx-v3/` (not published yet, and not yet tried with `sbx`). From a clone of this repository:
64-
65-```bash
66-cd /path/to/your/project
67-sbx run /path/to/mini-me/docker-sbx-v3/kits/mm-tui . -- agent.dmr.yaml
68-sbx create --name mm-acp /path/to/mini-me/docker-sbx-v3/kits/mm-acp . --kit-arg config=agent.dmr.yaml
69-```
70-
71-With the v3 kits, give `config` a path relative to the project: the workspace is mounted at `/home/agent/workspace`, so a `/Users/…` path does not exist inside the sandbox.
72-
73-Full guides: [Run mini-me in a Docker Sandbox](docs/en/how-to/run-in-a-docker-sandbox.md) (v2 kits, MCP, variants) and [Run mini-me with the v3 sandbox kits](docs/en/how-to/run-with-sandbox-kits-v3.md).
@@ -2,7 +2,7 @@
2 2
3 ```bash3 ```bash
4 # download the binary release in https://rickub.com/bots-garden/mini-me/releases4 # download the binary release in https://rickub.com/bots-garden/mini-me/releases
5-VERSION=0.2.15+VERSION=0.2.4
6 curl -fsSLO "https://rickub.com/bots-garden/mini-me/releases/download/v${VERSION}/mm-${VERSION}-darwin-arm64"6 curl -fsSLO "https://rickub.com/bots-garden/mini-me/releases/download/v${VERSION}/mm-${VERSION}-darwin-arm64"
7 chmod +x ./mm-${VERSION}-darwin-arm647 chmod +x ./mm-${VERSION}-darwin-arm64
8 xattr -cr ./mm-${VERSION}-darwin-arm648 xattr -cr ./mm-${VERSION}-darwin-arm64
@@ -10,64 +10,3 @@ sudo rm -f /usr/local/bin/mm
10 sudo cp ./mm-${VERSION}-darwin-arm64 /usr/local/bin/mm10 sudo cp ./mm-${VERSION}-darwin-arm64 /usr/local/bin/mm
11 ```11 ```
12 12
13-## Use `mm` in a Docker Sandbox (the two kits)
14-
15-Instead of installing the binary, `mm` can run inside a [Docker Sandbox](https://docs.docker.com/ai/sandboxes/): every command the model runs and every file it edits then happens in a container, on your mounted project. Two kits are published on Docker Hub at mm's version; each one brings the `k33g/mm-sandbox` image with `mm` in it, so nothing is built on your Mac.
16-
17-| Kit | For |
18-|---|---|
19-| `k33g/mm-tui:0.2.1` | the window mode (`mm -tui`) in your terminal |
20-| `k33g/mm-acp:0.2.1` | an editor that speaks the Agent Client Protocol (Zed, …) |
21-
22-You need Docker Desktop with the `sbx` command, and your model server (Docker Model Runner or llama-server) running on the Mac. Inside the sandbox, `localhost` is the sandbox itself: `agent.dmr.yaml` already falls back to `host.docker.internal`, which reaches the Mac.
23-
24-### Window mode: `mm-tui`
25-
26-From the project you want `mm` to work on:
27-
28-```bash
29-cd /path/to/your/project
30-sbx kit inspect k33g/mm-tui:0.2.1 # optional: what the kit declares
31-sbx run k33g/mm-tui:0.2.1 . -- agent.dmr.yaml
32-```
33-
34-What follows `--` is `mm`'s own command line (here the configuration file, relative to the project). `sbx ls` lists the sandboxes; `sbx run --name <name>` re-attaches to one.
35-
36-### From an editor: `mm-acp`
37-
38-Create the sandbox once, from the project the editor will open, with the configuration file baked in:
39-
40-```bash
41-cd /path/to/your/project
42-sbx create --name mm-acp k33g/mm-acp:0.2.1 . --kit-arg config=agent.dmr.yaml
43-```
44-
45-Then register it in Zed's `settings.json`:
46-
47-```json
48-{
49- "agent_servers": {
50- "mini-me (sandbox)": {
51- "type": "custom",
52- "command": "sbx",
53- "args": ["exec", "-i", "mm-acp", "mm", "-acp"]
54- }
55- }
56-}
57-```
58-
59-If Zed cannot find `sbx`, put the absolute path given by `which sbx` in `"command"`. One sandbox per project: give each one its own `--name` and its own entry in Zed. `sbx rm mm-acp` removes a sandbox; your project directory is not touched.
60-
61-### The v3 kits
62-
63-The same two kits also exist for the kit specification v3, in `docker-sbx-v3/` (not published yet, and not yet tried with `sbx`). From a clone of this repository:
64-
65-```bash
66-cd /path/to/your/project
67-sbx run /path/to/mini-me/docker-sbx-v3/kits/mm-tui . -- agent.dmr.yaml
68-sbx create --name mm-acp /path/to/mini-me/docker-sbx-v3/kits/mm-acp . --kit-arg config=agent.dmr.yaml
69-```
70-
71-With the v3 kits, give `config` a path relative to the project: the workspace is mounted at `/home/agent/workspace`, so a `/Users/…` path does not exist inside the sandbox.
72-
73-Full guides: [Run mini-me in a Docker Sandbox](docs/en/how-to/run-in-a-docker-sandbox.md) (v2 kits, MCP, variants) and [Run mini-me with the v3 sandbox kits](docs/en/how-to/run-with-sandbox-kits-v3.md).
modified docker-sbx-v3/kits/mm-acp/mm-acp.yaml +1 -1
@@ -48,7 +48,7 @@ args:
4848 pattern: '^[a-z0-9][a-z0-9._/:-]*$'
4949 buildArg: MM_IMAGE
5050 tag:
51- default: "0.2.3"
51+ default: "0.2.4"
5252 description: >-
5353 Tag of the template image: mm's version without the "v", as
5454 docker-sbx-v3/build.sh tags it (and rewrites this default to). Also the
@@ -48,7 +48,7 @@ args:
48 pattern: '^[a-z0-9][a-z0-9._/:-]*$'48 pattern: '^[a-z0-9][a-z0-9._/:-]*$'
49 buildArg: MM_IMAGE49 buildArg: MM_IMAGE
50 tag:50 tag:
51- default: "0.2.3"51+ default: "0.2.4"
52 description: >-52 description: >-
53 Tag of the template image: mm's version without the "v", as53 Tag of the template image: mm's version without the "v", as
54 docker-sbx-v3/build.sh tags it (and rewrites this default to). Also the54 docker-sbx-v3/build.sh tags it (and rewrites this default to). Also the
modified docker-sbx-v3/kits/mm-tui/mm-tui.yaml +1 -1
@@ -48,7 +48,7 @@ args:
4848 pattern: '^[a-z0-9][a-z0-9._/:-]*$'
4949 buildArg: MM_IMAGE
5050 tag:
51- default: "0.2.3"
51+ default: "0.2.4"
5252 description: >-
5353 Tag of the template image: mm's version without the "v", as
5454 docker-sbx-v3/build.sh tags it (and rewrites this default to). Also the
@@ -48,7 +48,7 @@ args:
48 pattern: '^[a-z0-9][a-z0-9._/:-]*$'48 pattern: '^[a-z0-9][a-z0-9._/:-]*$'
49 buildArg: MM_IMAGE49 buildArg: MM_IMAGE
50 tag:50 tag:
51- default: "0.2.3"51+ default: "0.2.4"
52 description: >-52 description: >-
53 Tag of the template image: mm's version without the "v", as53 Tag of the template image: mm's version without the "v", as
54 docker-sbx-v3/build.sh tags it (and rewrites this default to). Also the54 docker-sbx-v3/build.sh tags it (and rewrites this default to). Also the