Skip to content

Loss of context between models #462

@p-b--

Description

@p-b--

Issue

In early versions of cecli and aider, my typical flow would operate like this:

  1. in ask mode - get a plan going, identify the changes i would want to make (often in a planning file)
  2. switch to code mode and depending on the complexity either do: /code go do that, or switch to code mode and ask it to execute various steps in the plan.
  3. Critically - when I switch to the code mode, I would first switch models to a lower cost one, e.g. gemini-flash, sonnet, etc

I've noticed in recent versions of cecli, when I do that model switch, the "go do that" does not seem to include the prior context to write the code.

When I try to use a single model to do everything (whether thinking or not) I found I get better results than trying to switch between two models along with the execution modes.

Version and model info

cecli: 0.97.2

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions