mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-03 07:18:03 +01:00
v1.91.335.0 fix(capy): a session with no checkout reads the factory.md and preferences.yaml beside SKILL.md (GST-274) (#3643)
* fix(capy): a session with no checkout reads the factory.md and preferences.yaml beside SKILL.md (GST-274) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * fix(capy): a for=none session reads preferences.yaml even when an old checkout is on the machine (GST-274 review) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> * v1.91.335.0 stamp Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --------- Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
1 parent
b61744517c
commit
723b73ea89
7 files changed
+67
-4
No files matched your search
@@ -163,6 +163,13 @@ good, edit or delete that line; `gstack-config unset agent_model` clears this
|
||||
machine only. Copying a newer `capy/skill/gstack/` over the skill folder leaves
|
||||
`preferences.yaml` alone, because the shipped folder has no such file.
|
||||
|
||||
A Capy session with no gstack checkout (a Captain or coordinator that runs
|
||||
`install.sh --check --for none`) can't run the resolver, so the skill tells it
|
||||
to read the `agent_model` line itself. There a family means the newest model of
|
||||
that family the host lists, while the resolver maps each family to the id in
|
||||
its table (today they agree: `opus` is `anthropic/claude-opus-5-5`). Anything
|
||||
it can't use means the session keeps its own model and says so.
|
||||
|
||||
## Reasoning effort
|
||||
|
||||
Codex calls carry a `model_reasoning_effort`. It follows the same shape as the
|
||||
|
||||
Reference in new issue
Block a user