Skip to content

/speckit.implement - stay in same chat session or open a new one? #1145

Closed

Description

@wangyuqiang9509
No description provided.

Activity

  1. acgxv commented on Nov 10, 2025

    @acgxv

    This totally depends on your model’s context length.

    "Remember" everything is always good for a machine.

  2. wangyuqiang9509 commented on Nov 10, 2025

    @wangyuqiang9509
    Author

    This totally depends on your model’s context length.这完全取决于您的模型的上下文长度。

    "Remember" everything is always good for a machine."记住" 对机器来说,一切总是好的。

    Thank you for your question. Since the context length will be exceeded after a few rounds of conversation, I'd like to know whether it's better to start a new chat window or continue in the current one when the context is exceeded.

  3. acgxv commented on Nov 10, 2025

    @acgxv

    You’ll have to open a new one sometimes. You can’t be sure the next one won’t exceed the context window.

    Essentially, you don’t need to worry about this. Progress is recorded in task.md and each task is independent.

    The downside is that the new command takes some time or tokens to recover the latest state.

    Alternatively, you could tell your agent to summarise progress to a file when it finishes and then check the progress file in the next round.

  4. wangyuqiang9509 commented on Nov 10, 2025

    @wangyuqiang9509
    Author

    You’ll have to open a new one sometimes. You can’t be sure the next one won’t exceed the context window.

    Essentially, you don’t need to worry about this. Progress is recorded in task.md and each task is independent.

    The downside is that the new command takes some time or tokens to recover the latest state.

    Alternatively, you could tell your agent to summarise progress to a file when it finishes and then check the progress file in the next round.

    非常感谢

  5. changed the title [-]/speckit.implement 阶段是一直在同一个对话框中一直到结束还是不断开启新的对话框然后再输入执行命令哪种方式更好[/-] [+]/speckit.implement - stay in same chat session or open a new one?[/+] on Nov 15, 2025
  6. locked and limited conversation to collaborators on Nov 15, 2025
  7. converted this issue into a discussion #1188 on Nov 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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