Pascal AndréandBohdan Triapitsyn
49a1424e5f
* feat: add French locale runtime Add French to OpenChamber's shared i18n runtime, dictionaries, and parity tests so the existing language picker can load a complete fr locale across shared UI surfaces. * fix: localize shared UI formatting Remove remaining shared UI locale hardcodings so dates, numbers, and first-party helper copy follow the active app locale instead of leaking English on French surfaces. * feat: localize VS Code French surfaces Localize VS Code bootstrap, native runtime messages, panel titles, and manifest contribution strings so French users get consistent first-party copy across the extension experience. * fix: TASK-2026-05-30-008 correct French review findings Fix broken French relative-time and weekday strings reported on PR #1482 and restore proper import order in quota utils without broadening scope. * fix: TASK-2026-05-30-008 address final PR review comments Capture the localized More Info label once in the VS Code CLI-missing flow and replace the remaining inline French-only utility strings with dictionary-driven copy plus required locale keys. * fix: TASK-2026-05-30-008 normalize French glossary Correct glossary-level French terminology on the live PR branch, keeping canonical technical terms like PR, worktree, stash, HEAD, Mermaid, Markdown, remote, and session while replacing misleading literal translations. * fix: TASK-2026-05-30-008 refine French terminology pass Clean up remaining glossary mistakes on the French PR branch, especially around Mermaid, Markdown, PR, worktree, stash, branch, remote, and commit terminology, while keeping behavior unchanged. * fix: TASK-2026-05-30-008 clean remaining French false friends Correct the SOCKS5 mistranslation and a final small set of obvious false-friend technical nouns on the French branch without changing behavior. * fix: TASK-2026-05-30-008 correct French glossary terms Replace remaining false-friend translations in the French UI dictionaries and normalize technical labels for the French PR branch. * fix: TASK-2026-05-30-008 remove remaining French Mermaid false friend Replace the last confirmed Sirène translation with Mermaid and re-run the requested blacklist and build verification on the PR branch. * fix: TASK-2026-05-30-008 enforce French glossary policy Keep skill/PR/worktree/remote terminology developer-credible in French and remove remaining machine-translated Git and settings copy. * fix: TASK-2026-05-30-008 keep prompt terminology in French Replace remaining technical invite translations with prompt wording across scheduled tasks, multi-run, prompt templates, and Magic Prompts. * fix: TASK-2026-05-30-008 finalize French terminology cleanup Polish remaining worktree/remote wording, remove visible metadata leakage, and correct final Git and settings labels on the French PR branch. * fix: TASK-2026-05-30-008 polish final French strings Correct the last aria-like artifacts and awkward worktree/remote/GitHub URL phrasing in the French dictionaries. * fix: TASK-2026-05-30-008 normalize final French glossary framing Tighten the last worktree/remote/checkout wording and fix remaining French grammar around canonical technical terms. * fix: TASK-2026-05-30-008 align final developer glossary wording Normalize the last French framing around canonical developer terms like worktree, remote, prompt, and checkout. * fix: TASK-2026-05-30-008 harmonize final French sentence framing Replace the last raw franglais around checkout, remote, worktree, and prompt-facing labels with more natural French framing while keeping the chosen technical terms. * fix: TASK-2026-05-30-008 add compact relative date keys Replace French-specific prefix stripping in compact session date labels with dedicated i18n keys across locale dictionaries, preserving existing compact label output while making French wording robust. * docs: add French documentation * docs: mention French locale folder --------- Co-authored-by: Bohdan Triapitsyn <artmore@protonmail.com>
35 lines
1.6 KiB
Plaintext
35 lines
1.6 KiB
Plaintext
---
|
||
title: Multi-run
|
||
description: Lancez le même prompt sur plusieurs modèles ou sessions à la fois.
|
||
---
|
||
|
||
# Multi-run
|
||
|
||
Multi-run lance plusieurs sessions depuis un seul formulaire — pratique pour essayer la même tâche avec différents modèles et comparer les résultats. Ouvrez-le depuis le bouton en haut de la barre latérale des sessions.
|
||
|
||
## Démarrer un multi-run
|
||
|
||
1. Ouvrez le lanceur multi-run.
|
||
2. Choisissez le projet et nommez le groupe d’exécutions.
|
||
3. Écrivez le prompt et choisissez les modèles qui doivent l’exécuter (jusqu’à cinq par groupe).
|
||
4. Choisissez si vous voulez **isoler les exécutions**.
|
||
5. Lancez.
|
||
|
||
Chaque modèle reçoit sa propre session, et toutes commencent avec votre prompt.
|
||
|
||
## Exécutions isolées
|
||
|
||
Activez **isolate runs** pour donner à chaque exécution son propre [worktree](/worktrees/) et sa propre branche, afin qu’elles ne touchent jamais les mêmes fichiers. Cela nécessite un dépôt git — l’option est désactivée automatiquement pour les dossiers qui n’en sont pas un. Choisissez la branche de départ des exécutions.
|
||
|
||
Sans isolation, chaque exécution est une session simple dans le dossier du projet.
|
||
|
||
## Comparer les résultats
|
||
|
||
Chaque exécution est une session normale que vous pouvez ouvrir, lire, conserver ou jeter. Si vous avez lancé des exécutions pour comparer des approches, relisez-les côte à côte et continuez avec la meilleure.
|
||
|
||
Si une seule exécution ne démarre pas, les autres se lancent quand même — vous verrez simplement moins de sessions que demandé.
|
||
|
||
## Pages liées
|
||
|
||
- [Sessions worktree](/worktrees/) — comment l’isolation fonctionne sous le capot
|