Active Configuration edit section ignored in --replay --edit
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16
- Forks
- 3
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 121
Description
As a user, when I change the model name in a --replay --edit, such as when trying to downgrade the model after a refusal, I expect the edited configuration to be parsed and applied.
# Active Configuration
> NOTE: You can edit this configuration to apply it to the current conversation.
> If the configuration is invalid, the editor will re-open.
>
> Only the most relevant configuration is shown here, but you can add any
> configuration properties you want to apply.
```toml
[assistant.model.id]
provider = "anthropic"
name = "claude-opus-4-8"
[assistant.model.parameters]
reasoning = "auto"
```
Analysis: this is a delayed-application error that you could call an off-by-one error. The state is stored but the previous state is applied. A second --replay --edit with no edits will apply the model change.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the --replay --edit handling and trace when the edited Active Configuration is parsed, stored, and applied. Reproduce the model-name change and confirm that it takes effect in the same invocation, while invalid configuration still causes the editor to reopen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ai, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100