rickub
bots-garden/mini-mepublic Fork
⑂ f3a4b95
Branches
feature/acp-client-tools feature/agents-file feature/ask-agent-hooks feature/ask-cli feature/decider-no-tools 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-me-as-a-sdk 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 v1.0.1 v1.0.2 v1.0.3 v1.0.4 v1.0.5 v1.0.6 v1.0.7 v1.0.8 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-11-13T14:13:18+01:00 Browse files
f3a4b95 parent: 16cca31
modified .tickets/issues/0209-mm-sbxinit-no-agent-config-for-a-mm-project-with-a.yaml +12 -3
@@ -1,12 +1,12 @@
11 # Managed by IssueSpec. Hand edits are welcome; keep the schema valid.
22 id: 209
33 title: "mm sbxinit: no AGENT_CONFIG / PROJECT_DIR for a .mm project with a kit that ships mm 1.0.7+"
4-state: open
4+state: closed
55 author:
66 name: k33g
77 email: ph.charriere@gmail.com
88 createdAt: 2026-11-13T13:00:20.000Z
9-updatedAt: 2026-11-13T13:06:01.000Z
9+updatedAt: 2026-11-13T13:09:56.000Z
1010 labels:
1111 - enhancement
1212 - kind::feature
@@ -84,12 +84,14 @@ tasks:
8484 closedAt: 2026-11-13T13:06:01.000Z
8585 - id: 4
8686 title: "Check in sbx: mm starts in the workspace (terminal) and under sbx exec (ACP)"
87- state: open
87+ state: closed
8888 priority: none
8989 author:
9090 name: k33g
9191 email: ph.charriere@gmail.com
9292 createdAt: 2026-11-13T13:00:20.000Z
93+ updatedAt: 2026-11-13T13:09:56.000Z
94+ closedAt: 2026-11-13T13:09:56.000Z
9395 - id: 5
9496 title: "Tests, docs EN+FR (incl. the Zed settings for a sandboxed .mm project)"
9597 state: closed
@@ -117,3 +119,10 @@ comments:
117119 Implemented (not committed, on main's working tree): [internal/sbxinit/mmfolder.go](internal/sbxinit/mmfolder.go) no longer writes `args.PROJECT_DIR` nor `env.AGENT_CONFIG` for a `.mm` project, and a comment says why; [internal/sbxinit/sbxinit.go](internal/sbxinit/sbxinit.go) prints and writes the `sbx env` commands without `--env-arg`. Mounts unchanged (`.mm` read-only, `sessions.dir` / `trace.dir` writable, relative paths). Tests updated (`TestMainMountsTheMMFolderReadOnly`, `TestMMFolderInASubWorkspace`); `go test ./...` green. The output matches the user's hand-fixed `bob-coder/sbxenv.yaml`.
118120 Docs EN+FR: how-to sandbox § `.mm` (example without args/env, what to do if the banner says `config: built-in defaults`, how to clean a file written by sbxinit 1.0.7, Zed settings with `sbx exec … mm -acp -config <absolute path>`), CLI reference `--agent`.
119121 Task 4 stays open: check in sbx that the kit's mm starts in the workspace (banner `config: .mm/agent.yaml`), and the working directory under `sbx exec`.
122+ - id: 3
123+ author:
124+ name: k33g
125+ email: ph.charriere@gmail.com
126+ createdAt: 2026-11-13T13:09:56.000Z
127+ body: |
128+ Task 4 checked by the user in a Docker Sandbox (bob-coder, mini-me-kit 0.1.5): mm starts in the workspace and finds .mm/agent.yaml without PROJECT_DIR. Closed for release v1.0.8.
@@ -1,12 +1,12 @@
1 # Managed by IssueSpec. Hand edits are welcome; keep the schema valid.1 # Managed by IssueSpec. Hand edits are welcome; keep the schema valid.
2 id: 2092 id: 209
3 title: "mm sbxinit: no AGENT_CONFIG / PROJECT_DIR for a .mm project with a kit that ships mm 1.0.7+"3 title: "mm sbxinit: no AGENT_CONFIG / PROJECT_DIR for a .mm project with a kit that ships mm 1.0.7+"
4-state: open4+state: closed
5 author:5 author:
6 name: k33g6 name: k33g
7 email: ph.charriere@gmail.com7 email: ph.charriere@gmail.com
8 createdAt: 2026-11-13T13:00:20.000Z8 createdAt: 2026-11-13T13:00:20.000Z
9-updatedAt: 2026-11-13T13:06:01.000Z9+updatedAt: 2026-11-13T13:09:56.000Z
10 labels:10 labels:
11 - enhancement11 - enhancement
12 - kind::feature12 - kind::feature
@@ -84,12 +84,14 @@ tasks:
84 closedAt: 2026-11-13T13:06:01.000Z84 closedAt: 2026-11-13T13:06:01.000Z
85 - id: 485 - id: 4
86 title: "Check in sbx: mm starts in the workspace (terminal) and under sbx exec (ACP)"86 title: "Check in sbx: mm starts in the workspace (terminal) and under sbx exec (ACP)"
87- state: open87+ state: closed
88 priority: none88 priority: none
89 author:89 author:
90 name: k33g90 name: k33g
91 email: ph.charriere@gmail.com91 email: ph.charriere@gmail.com
92 createdAt: 2026-11-13T13:00:20.000Z92 createdAt: 2026-11-13T13:00:20.000Z
93+ updatedAt: 2026-11-13T13:09:56.000Z
94+ closedAt: 2026-11-13T13:09:56.000Z
93 - id: 595 - id: 5
94 title: "Tests, docs EN+FR (incl. the Zed settings for a sandboxed .mm project)"96 title: "Tests, docs EN+FR (incl. the Zed settings for a sandboxed .mm project)"
95 state: closed97 state: closed
@@ -117,3 +119,10 @@ comments:
117 Implemented (not committed, on main's working tree): [internal/sbxinit/mmfolder.go](internal/sbxinit/mmfolder.go) no longer writes `args.PROJECT_DIR` nor `env.AGENT_CONFIG` for a `.mm` project, and a comment says why; [internal/sbxinit/sbxinit.go](internal/sbxinit/sbxinit.go) prints and writes the `sbx env` commands without `--env-arg`. Mounts unchanged (`.mm` read-only, `sessions.dir` / `trace.dir` writable, relative paths). Tests updated (`TestMainMountsTheMMFolderReadOnly`, `TestMMFolderInASubWorkspace`); `go test ./...` green. The output matches the user's hand-fixed `bob-coder/sbxenv.yaml`.119 Implemented (not committed, on main's working tree): [internal/sbxinit/mmfolder.go](internal/sbxinit/mmfolder.go) no longer writes `args.PROJECT_DIR` nor `env.AGENT_CONFIG` for a `.mm` project, and a comment says why; [internal/sbxinit/sbxinit.go](internal/sbxinit/sbxinit.go) prints and writes the `sbx env` commands without `--env-arg`. Mounts unchanged (`.mm` read-only, `sessions.dir` / `trace.dir` writable, relative paths). Tests updated (`TestMainMountsTheMMFolderReadOnly`, `TestMMFolderInASubWorkspace`); `go test ./...` green. The output matches the user's hand-fixed `bob-coder/sbxenv.yaml`.
118 Docs EN+FR: how-to sandbox § `.mm` (example without args/env, what to do if the banner says `config: built-in defaults`, how to clean a file written by sbxinit 1.0.7, Zed settings with `sbx exec … mm -acp -config <absolute path>`), CLI reference `--agent`.120 Docs EN+FR: how-to sandbox § `.mm` (example without args/env, what to do if the banner says `config: built-in defaults`, how to clean a file written by sbxinit 1.0.7, Zed settings with `sbx exec … mm -acp -config <absolute path>`), CLI reference `--agent`.
119 Task 4 stays open: check in sbx that the kit's mm starts in the workspace (banner `config: .mm/agent.yaml`), and the working directory under `sbx exec`.121 Task 4 stays open: check in sbx that the kit's mm starts in the workspace (banner `config: .mm/agent.yaml`), and the working directory under `sbx exec`.
122+ - id: 3
123+ author:
124+ name: k33g
125+ email: ph.charriere@gmail.com
126+ createdAt: 2026-11-13T13:09:56.000Z
127+ body: |
128+ Task 4 checked by the user in a Docker Sandbox (bob-coder, mini-me-kit 0.1.5): mm starts in the workspace and finds .mm/agent.yaml without PROJECT_DIR. Closed for release v1.0.8.
modified .tickets/milestones.yaml +1 -1
@@ -61,4 +61,4 @@ milestones:
6161 state: closed
6262 dueOn: 2026-11-14
6363 - title: v1.0.8
64- state: open
64+ state: closed
@@ -61,4 +61,4 @@ milestones:
61 state: closed61 state: closed
62 dueOn: 2026-11-1462 dueOn: 2026-11-14
63 - title: v1.0.863 - title: v1.0.8
64- state: open64+ state: closed
modified INSTALL.LINUX.md +1 -1
@@ -2,7 +2,7 @@
22
33 ```bash
44 # download the binary release in https://rickub.com/bots-garden/mini-me/releases
5-VERSION=1.0.7
5+VERSION=1.0.8
66 case "$(uname -m)" in
77 x86_64) ARCH=amd64 ;;
88 aarch64|arm64) ARCH=arm64 ;;
@@ -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=1.0.75+VERSION=1.0.8
6 case "$(uname -m)" in6 case "$(uname -m)" in
7 x86_64) ARCH=amd64 ;;7 x86_64) ARCH=amd64 ;;
8 aarch64|arm64) ARCH=arm64 ;;8 aarch64|arm64) ARCH=arm64 ;;
modified INSTALL.MACOS.md +4 -4
@@ -2,7 +2,7 @@
22
33 Short version:
44 ```bash
5-VERSION=1.0.7
5+VERSION=1.0.8
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 sudo rm -f /usr/local/bin/mm
@@ -14,7 +14,7 @@ From v1.0.5, the macOS binary is signed with a Developer ID and notarized by App
1414
1515 ```bash
1616 # download the binary release in https://rickub.com/bots-garden/mini-me/releases
17-VERSION=1.0.7
17+VERSION=1.0.8
1818 curl -fsSLO "https://rickub.com/bots-garden/mini-me/releases/download/v${VERSION}/mm-${VERSION}-darwin-arm64"
1919
2020 # optional: check the download against the release's checksums
@@ -34,8 +34,8 @@ mm --version
3434 The signature check should print:
3535
3636 ```
37-./mm-1.0.7-darwin-arm64: valid on disk
38-./mm-1.0.7-darwin-arm64: satisfies its Designated Requirement
37+./mm-1.0.8-darwin-arm64: valid on disk
38+./mm-1.0.8-darwin-arm64: satisfies its Designated Requirement
3939 Identifier=com.bots-garden.mm
4040 Authority=Developer ID Application: Philippe Charriere (SNLLBZP9V9)
4141 TeamIdentifier=SNLLBZP9V9
@@ -2,7 +2,7 @@
2 2
3 Short version:3 Short version:
4 ```bash4 ```bash
5-VERSION=1.0.75+VERSION=1.0.8
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 sudo rm -f /usr/local/bin/mm8 sudo rm -f /usr/local/bin/mm
@@ -14,7 +14,7 @@ From v1.0.5, the macOS binary is signed with a Developer ID and notarized by App
14 14
15 ```bash15 ```bash
16 # download the binary release in https://rickub.com/bots-garden/mini-me/releases16 # download the binary release in https://rickub.com/bots-garden/mini-me/releases
17-VERSION=1.0.717+VERSION=1.0.8
18 curl -fsSLO "https://rickub.com/bots-garden/mini-me/releases/download/v${VERSION}/mm-${VERSION}-darwin-arm64"18 curl -fsSLO "https://rickub.com/bots-garden/mini-me/releases/download/v${VERSION}/mm-${VERSION}-darwin-arm64"
19 19
20 # optional: check the download against the release's checksums20 # optional: check the download against the release's checksums
@@ -34,8 +34,8 @@ mm --version
34 The signature check should print:34 The signature check should print:
35 35
36 ```36 ```
37-./mm-1.0.7-darwin-arm64: valid on disk37+./mm-1.0.8-darwin-arm64: valid on disk
38-./mm-1.0.7-darwin-arm64: satisfies its Designated Requirement38+./mm-1.0.8-darwin-arm64: satisfies its Designated Requirement
39 Identifier=com.bots-garden.mm39 Identifier=com.bots-garden.mm
40 Authority=Developer ID Application: Philippe Charriere (SNLLBZP9V9)40 Authority=Developer ID Application: Philippe Charriere (SNLLBZP9V9)
41 TeamIdentifier=SNLLBZP9V941 TeamIdentifier=SNLLBZP9V9
modified INSTALL.WINDOWS.md +1 -1
@@ -4,7 +4,7 @@ In PowerShell (no administrator rights needed):
44
55 ```powershell
66 # download the binary release in https://rickub.com/bots-garden/mini-me/releases
7-$Version = "1.0.7"
7+$Version = "1.0.8"
88 $Arch = if ($env:PROCESSOR_ARCHITECTURE -eq "ARM64") { "arm64" } else { "amd64" }
99 $Asset = "mm-$Version-windows-$Arch.exe"
1010 $Base = "https://rickub.com/bots-garden/mini-me/releases/download/v$Version"
@@ -4,7 +4,7 @@ In PowerShell (no administrator rights needed):
4 4
5 ```powershell5 ```powershell
6 # download the binary release in https://rickub.com/bots-garden/mini-me/releases6 # download the binary release in https://rickub.com/bots-garden/mini-me/releases
7-$Version = "1.0.7"7+$Version = "1.0.8"
8 $Arch = if ($env:PROCESSOR_ARCHITECTURE -eq "ARM64") { "arm64" } else { "amd64" }8 $Arch = if ($env:PROCESSOR_ARCHITECTURE -eq "ARM64") { "arm64" } else { "amd64" }
9 $Asset = "mm-$Version-windows-$Arch.exe"9 $Asset = "mm-$Version-windows-$Arch.exe"
10 $Base = "https://rickub.com/bots-garden/mini-me/releases/download/v$Version"10 $Base = "https://rickub.com/bots-garden/mini-me/releases/download/v$Version"
modified release-notes/README.md +1 -0
@@ -4,6 +4,7 @@ One note per tag, in English (`.en.md`) and French (`.fr.md`). Rebuilt on 2026-1
44
55 | Version | Date | Summary | |
66 |---|---|---|---|
7+| [v1.0.8](v1.0.8.en.md) | not tagged yet | `mm sbxinit` writes a simpler `sbxenv.yaml` for a `.mm` project: no `PROJECT_DIR` argument and no `--env-arg` on the `sbx env` commands. | [FR](v1.0.8.fr.md) |
78 | [v1.0.7](v1.0.7.en.md) | not tagged yet | A project can keep its agent in a `.mm` folder, which `mm init`, `mm sbxinit` and the new `mm skillcreate` all know, and models such as SmolLM3, whose chat template reads its tools from `xml_tools`, can call mm's tools. | [FR](v1.0.7.fr.md) |
89 | [v1.0.6](v1.0.6.en.md) | not tagged yet | An ACP client can lend the agent its own functions as tools, and mini-me runs on Kronk, the Go inference server of Ardan Labs. | [FR](v1.0.6.fr.md) |
910 | [v1.0.5](v1.0.5.en.md) | 2026-11-07 | `mm dockerinit` and `mm sbxinit` write the files to run mini-me in a container or a Docker Sandbox, `mm init` gives the agent its name, two vibe-coding demos (Go and Swift), and a macOS binary signed and notarized by Apple. | [FR](v1.0.5.fr.md) |
@@ -4,6 +4,7 @@ One note per tag, in English (`.en.md`) and French (`.fr.md`). Rebuilt on 2026-1
4 4
5 | Version | Date | Summary | |5 | Version | Date | Summary | |
6 |---|---|---|---|6 |---|---|---|---|
7+| [v1.0.8](v1.0.8.en.md) | not tagged yet | `mm sbxinit` writes a simpler `sbxenv.yaml` for a `.mm` project: no `PROJECT_DIR` argument and no `--env-arg` on the `sbx env` commands. | [FR](v1.0.8.fr.md) |
7 | [v1.0.7](v1.0.7.en.md) | not tagged yet | A project can keep its agent in a `.mm` folder, which `mm init`, `mm sbxinit` and the new `mm skillcreate` all know, and models such as SmolLM3, whose chat template reads its tools from `xml_tools`, can call mm's tools. | [FR](v1.0.7.fr.md) |8 | [v1.0.7](v1.0.7.en.md) | not tagged yet | A project can keep its agent in a `.mm` folder, which `mm init`, `mm sbxinit` and the new `mm skillcreate` all know, and models such as SmolLM3, whose chat template reads its tools from `xml_tools`, can call mm's tools. | [FR](v1.0.7.fr.md) |
8 | [v1.0.6](v1.0.6.en.md) | not tagged yet | An ACP client can lend the agent its own functions as tools, and mini-me runs on Kronk, the Go inference server of Ardan Labs. | [FR](v1.0.6.fr.md) |9 | [v1.0.6](v1.0.6.en.md) | not tagged yet | An ACP client can lend the agent its own functions as tools, and mini-me runs on Kronk, the Go inference server of Ardan Labs. | [FR](v1.0.6.fr.md) |
9 | [v1.0.5](v1.0.5.en.md) | 2026-11-07 | `mm dockerinit` and `mm sbxinit` write the files to run mini-me in a container or a Docker Sandbox, `mm init` gives the agent its name, two vibe-coding demos (Go and Swift), and a macOS binary signed and notarized by Apple. | [FR](v1.0.5.fr.md) |10 | [v1.0.5](v1.0.5.en.md) | 2026-11-07 | `mm dockerinit` and `mm sbxinit` write the files to run mini-me in a container or a Docker Sandbox, `mm init` gives the agent its name, two vibe-coding demos (Go and Swift), and a macOS binary signed and notarized by Apple. | [FR](v1.0.5.fr.md) |
added release-notes/v1.0.8.en.md +39 -0
new file mode 100644
@@ -0,0 +1,39 @@
1+# mini-me v1.0.8
2+
3+*[Version française](v1.0.8.fr.md)*
4+
5+`mm sbxinit` writes a simpler `sbxenv.yaml` for a `.mm` project: no `PROJECT_DIR` argument and no `--env-arg` on the `sbx env` commands.
6+
7+## New
8+
9+### `mm sbxinit` without `PROJECT_DIR` (#209)
10+
11+In v1.0.7, `mm sbxinit` wrote two more blocks for a project whose agent is `.mm/agent.yaml`: a required `PROJECT_DIR` argument, and `AGENT_CONFIG` built from it. Every `sbx env` command then needed `--env-arg PROJECT_DIR="$PWD"`. They were there so that the file would also work with a kit that ships an mm older than v1.0.7.
12+
13+`mm sbxinit` always writes the latest kit. From `mini-me-kit:0.1.5` on, the kit ships mm 1.0.7 or later, which finds `.mm/agent.yaml` on its own when it starts in the workspace. The two blocks are gone, and so is the argument:
14+
15+```bash
16+sbx env create --force
17+sbx env run --force
18+```
19+
20+The mounts do not change. `.mm/` is still mounted read-only over the workspace, the agent file's `sessions.dir` and `trace.dir` are writable again, and every path is relative to the folder of `sbxenv.yaml`. A comment in the file says why it sets no `AGENT_CONFIG`.
21+
22+Checked in a Docker Sandbox with `mini-me-kit:0.1.5`: mm starts in the workspace and reads `.mm/agent.yaml` with no `PROJECT_DIR`.
23+
24+See [How to run mini-me in a Docker Sandbox](../docs/en/how-to/run-in-a-docker-sandbox.md).
25+
26+## Documentation
27+
28+- The Docker Sandbox guide, in its `.mm` section:
29+ - shows the file without `args` and `env`;
30+ - says what to do if the banner shows `config: built-in defaults`;
31+ - says how to clean a file written by `mm sbxinit` 1.0.7;
32+ - gives the editor settings (Zed) that run mm in the sandbox with `sbx exec … mm -acp -config <absolute path of .mm/agent.yaml>`.
33+- The CLI reference describes the new `mm sbxinit` output for a `.mm` project.
34+
35+## Upgrading
36+
37+- **Agent files do not change.** Replace the binary: see the install guides for [macOS](../INSTALL.MACOS.md), [Linux](../INSTALL.LINUX.md) and [Windows](../INSTALL.WINDOWS.md).
38+- **A `sbxenv.yaml` written by `mm sbxinit` 1.0.7 for a `.mm` project** still works. With a kit of 0.1.5 or later, you can remove its `args:` and `env:` blocks, then drop `--env-arg` from the commands. You can also run `mm sbxinit` again and answer `yes` to replace the file.
39+- A sandbox keeps the kit and the mounts it was created with. After changing the file, remove it once with the old command (`sbx env rm --force --env-arg PROJECT_DIR="$PWD"`), then create it again with `sbx env run --force`.
new file mode 100644
@@ -0,0 +1,39 @@
1+# mini-me v1.0.8
2+
3+*[Version française](v1.0.8.fr.md)*
4+
5+`mm sbxinit` writes a simpler `sbxenv.yaml` for a `.mm` project: no `PROJECT_DIR` argument and no `--env-arg` on the `sbx env` commands.
6+
7+## New
8+
9+### `mm sbxinit` without `PROJECT_DIR` (#209)
10+
11+In v1.0.7, `mm sbxinit` wrote two more blocks for a project whose agent is `.mm/agent.yaml`: a required `PROJECT_DIR` argument, and `AGENT_CONFIG` built from it. Every `sbx env` command then needed `--env-arg PROJECT_DIR="$PWD"`. They were there so that the file would also work with a kit that ships an mm older than v1.0.7.
12+
13+`mm sbxinit` always writes the latest kit. From `mini-me-kit:0.1.5` on, the kit ships mm 1.0.7 or later, which finds `.mm/agent.yaml` on its own when it starts in the workspace. The two blocks are gone, and so is the argument:
14+
15+```bash
16+sbx env create --force
17+sbx env run --force
18+```
19+
20+The mounts do not change. `.mm/` is still mounted read-only over the workspace, the agent file's `sessions.dir` and `trace.dir` are writable again, and every path is relative to the folder of `sbxenv.yaml`. A comment in the file says why it sets no `AGENT_CONFIG`.
21+
22+Checked in a Docker Sandbox with `mini-me-kit:0.1.5`: mm starts in the workspace and reads `.mm/agent.yaml` with no `PROJECT_DIR`.
23+
24+See [How to run mini-me in a Docker Sandbox](../docs/en/how-to/run-in-a-docker-sandbox.md).
25+
26+## Documentation
27+
28+- The Docker Sandbox guide, in its `.mm` section:
29+ - shows the file without `args` and `env`;
30+ - says what to do if the banner shows `config: built-in defaults`;
31+ - says how to clean a file written by `mm sbxinit` 1.0.7;
32+ - gives the editor settings (Zed) that run mm in the sandbox with `sbx exec … mm -acp -config <absolute path of .mm/agent.yaml>`.
33+- The CLI reference describes the new `mm sbxinit` output for a `.mm` project.
34+
35+## Upgrading
36+
37+- **Agent files do not change.** Replace the binary: see the install guides for [macOS](../INSTALL.MACOS.md), [Linux](../INSTALL.LINUX.md) and [Windows](../INSTALL.WINDOWS.md).
38+- **A `sbxenv.yaml` written by `mm sbxinit` 1.0.7 for a `.mm` project** still works. With a kit of 0.1.5 or later, you can remove its `args:` and `env:` blocks, then drop `--env-arg` from the commands. You can also run `mm sbxinit` again and answer `yes` to replace the file.
39+- A sandbox keeps the kit and the mounts it was created with. After changing the file, remove it once with the old command (`sbx env rm --force --env-arg PROJECT_DIR="$PWD"`), then create it again with `sbx env run --force`.
added release-notes/v1.0.8.fr.md +39 -0
new file mode 100644
@@ -0,0 +1,39 @@
1+# mini-me v1.0.8
2+
3+*[English version](v1.0.8.en.md)*
4+
5+`mm sbxinit` écrit un `sbxenv.yaml` plus simple pour un projet `.mm` : plus d'argument `PROJECT_DIR`, et plus de `--env-arg` dans les commandes `sbx env`.
6+
7+## Nouveautés
8+
9+### `mm sbxinit` sans `PROJECT_DIR` (#209)
10+
11+En v1.0.7, `mm sbxinit` écrivait deux blocs de plus pour un projet dont l'agent est `.mm/agent.yaml` : un argument `PROJECT_DIR` obligatoire, et `AGENT_CONFIG` construit à partir de lui. Chaque commande `sbx env` demandait alors `--env-arg PROJECT_DIR="$PWD"`. Ils servaient à ce que le fichier marche aussi avec un kit embarquant un mm antérieur à la v1.0.7.
12+
13+`mm sbxinit` écrit toujours le dernier kit. À partir de `mini-me-kit:0.1.5`, le kit embarque mm 1.0.7 ou plus récent, qui trouve `.mm/agent.yaml` tout seul quand il démarre dans le workspace. Les deux blocs disparaissent, et l'argument avec eux :
14+
15+```bash
16+sbx env create --force
17+sbx env run --force
18+```
19+
20+Les montages ne changent pas. `.mm/` reste monté en lecture seule par-dessus le workspace, le `sessions.dir` et le `trace.dir` du fichier d'agent redeviennent inscriptibles, et tous les chemins sont relatifs au dossier de `sbxenv.yaml`. Un commentaire dans le fichier explique pourquoi il ne fixe pas d'`AGENT_CONFIG`.
21+
22+Vérifié dans un Docker Sandbox avec `mini-me-kit:0.1.5` : mm démarre dans le workspace et lit `.mm/agent.yaml` sans `PROJECT_DIR`.
23+
24+Voir [Comment faire tourner mini-me dans un Docker Sandbox](../docs/fr/how-to/run-in-a-docker-sandbox.md).
25+
26+## Documentation
27+
28+- Le guide Docker Sandbox, dans sa section `.mm` :
29+ - montre le fichier sans `args` ni `env` ;
30+ - dit quoi faire si la bannière affiche `config: built-in defaults` ;
31+ - explique comment nettoyer un fichier écrit par `mm sbxinit` 1.0.7 ;
32+ - donne la configuration d'un éditeur (Zed) qui lance mm dans la sandbox avec `sbx exec … mm -acp -config <chemin absolu de .mm/agent.yaml>`.
33+- La référence CLI décrit la nouvelle sortie de `mm sbxinit` pour un projet `.mm`.
34+
35+## Mise à jour
36+
37+- **Les fichiers d'agent ne changent pas.** Remplacez le binaire : voir les guides d'installation pour [macOS](../INSTALL.MACOS.md), [Linux](../INSTALL.LINUX.md) et [Windows](../INSTALL.WINDOWS.md).
38+- **Un `sbxenv.yaml` écrit par `mm sbxinit` 1.0.7 pour un projet `.mm`** fonctionne toujours. Avec un kit 0.1.5 ou plus récent, vous pouvez retirer ses blocs `args:` et `env:`, puis enlever `--env-arg` des commandes. Vous pouvez aussi relancer `mm sbxinit` et répondre `yes` pour remplacer le fichier.
39+- Une sandbox garde le kit et les montages de sa création. Après avoir changé le fichier, supprimez-la une fois avec l'ancienne commande (`sbx env rm --force --env-arg PROJECT_DIR="$PWD"`), puis recréez-la avec `sbx env run --force`.
new file mode 100644
@@ -0,0 +1,39 @@
1+# mini-me v1.0.8
2+
3+*[English version](v1.0.8.en.md)*
4+
5+`mm sbxinit` écrit un `sbxenv.yaml` plus simple pour un projet `.mm` : plus d'argument `PROJECT_DIR`, et plus de `--env-arg` dans les commandes `sbx env`.
6+
7+## Nouveautés
8+
9+### `mm sbxinit` sans `PROJECT_DIR` (#209)
10+
11+En v1.0.7, `mm sbxinit` écrivait deux blocs de plus pour un projet dont l'agent est `.mm/agent.yaml` : un argument `PROJECT_DIR` obligatoire, et `AGENT_CONFIG` construit à partir de lui. Chaque commande `sbx env` demandait alors `--env-arg PROJECT_DIR="$PWD"`. Ils servaient à ce que le fichier marche aussi avec un kit embarquant un mm antérieur à la v1.0.7.
12+
13+`mm sbxinit` écrit toujours le dernier kit. À partir de `mini-me-kit:0.1.5`, le kit embarque mm 1.0.7 ou plus récent, qui trouve `.mm/agent.yaml` tout seul quand il démarre dans le workspace. Les deux blocs disparaissent, et l'argument avec eux :
14+
15+```bash
16+sbx env create --force
17+sbx env run --force
18+```
19+
20+Les montages ne changent pas. `.mm/` reste monté en lecture seule par-dessus le workspace, le `sessions.dir` et le `trace.dir` du fichier d'agent redeviennent inscriptibles, et tous les chemins sont relatifs au dossier de `sbxenv.yaml`. Un commentaire dans le fichier explique pourquoi il ne fixe pas d'`AGENT_CONFIG`.
21+
22+Vérifié dans un Docker Sandbox avec `mini-me-kit:0.1.5` : mm démarre dans le workspace et lit `.mm/agent.yaml` sans `PROJECT_DIR`.
23+
24+Voir [Comment faire tourner mini-me dans un Docker Sandbox](../docs/fr/how-to/run-in-a-docker-sandbox.md).
25+
26+## Documentation
27+
28+- Le guide Docker Sandbox, dans sa section `.mm` :
29+ - montre le fichier sans `args` ni `env` ;
30+ - dit quoi faire si la bannière affiche `config: built-in defaults` ;
31+ - explique comment nettoyer un fichier écrit par `mm sbxinit` 1.0.7 ;
32+ - donne la configuration d'un éditeur (Zed) qui lance mm dans la sandbox avec `sbx exec … mm -acp -config <chemin absolu de .mm/agent.yaml>`.
33+- La référence CLI décrit la nouvelle sortie de `mm sbxinit` pour un projet `.mm`.
34+
35+## Mise à jour
36+
37+- **Les fichiers d'agent ne changent pas.** Remplacez le binaire : voir les guides d'installation pour [macOS](../INSTALL.MACOS.md), [Linux](../INSTALL.LINUX.md) et [Windows](../INSTALL.WINDOWS.md).
38+- **Un `sbxenv.yaml` écrit par `mm sbxinit` 1.0.7 pour un projet `.mm`** fonctionne toujours. Avec un kit 0.1.5 ou plus récent, vous pouvez retirer ses blocs `args:` et `env:`, puis enlever `--env-arg` des commandes. Vous pouvez aussi relancer `mm sbxinit` et répondre `yes` pour remplacer le fichier.
39+- Une sandbox garde le kit et les montages de sa création. Après avoir changé le fichier, supprimez-la une fois avec l'ancienne commande (`sbx env rm --force --env-arg PROJECT_DIR="$PWD"`), puis recréez-la avec `sbx env run --force`.