Skip to content

Conversation

@t-proctor
Copy link
Contributor

No description provided.

@t-proctor t-proctor changed the title wip- agent auto accept agent auto accept Nov 21, 2025
@t-proctor t-proctor changed the title agent auto accept Agent Behavior Modes Nov 21, 2025
@t-proctor t-proctor requested a review from AidanAbd November 21, 2025 07:58
@t-proctor t-proctor marked this pull request as ready for review November 21, 2025 08:00
@t-proctor t-proctor changed the title Agent Behavior Modes agent behavior modes Nov 21, 2025
@t-proctor t-proctor force-pushed the tim/agent-auto-accept branch from 4e75835 to ba7cad9 Compare November 21, 2025 09:12
Copy link
Contributor

@AidanAbd AidanAbd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your instructions here contradict with some of the existing instructions like

<turn_structure>

## Turn Processing

Each turn processes one user message (question, request, cell execution result, or environment information).

## Turn Flow

1. Process user input
2. Update plan status if working on a plan
3. Execute actions (create/edit cells, ask questions, etc.)
4. Call `submit_response` with current state
5. Either continue (if `continue: true`) or wait for next input

## Turn End Requirement

**Every turn MUST end with `submit_response`**. After calling `submit_response`:

- If `continue: true` → Immediately proceed to next action
- If `continue: false` → Turn ends, wait for next user input or cell execution result

</turn_structure>

Might be better to inject the turn structure rather than just add on a bit at the end, and have each mode's turn structure be pretty specific to that mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants