In-Session Actions

┌─────┐   ┌─────┐   ┌─────┐   ┌─────┐   ┌─────┐
│  1  │ → │  2  │ → │  3  │ → │  4  │ → │  5  │
└─────┘   └─────┘   └─────┘   └─────┘   └─────┘
           
                   Edit here
                       ↓
┌─────┐   ┌─────┐   ┌─────┐    continue from here in
│  1  │ → │  2  │ → │  3  │ →  current session, or
└─────┘   └─────┘   └─────┘    copy to new session

    1. Hover over any of your previous messages
    2. Click the <Edit2 className="inline" size={16} /> `Edit` button that appears
    3. Make your changes in the inline editor
    4. Click `Edit in Place` to save your changes and reprompt goose

    goose removes all conversation history after the edited message and responds contextually from that point.

    :::warning Deleted Context
    With Edit in Place, subsequent conversation history is permanently deleted from the session and removed from goose's context. Use this option only if you don't need goose to remember the context that follows the edited message.
    :::

</TabItem>
<TabItem value="cli" label="goose CLI">
    Message editing options are not available in the goose CLI.
</TabItem>

    goose creates a new session with conversation history up to and including your edited message. The new session is named "(edited)" and the original session remains unchanged.

    :::tip Fork vs Duplicate
    - **Fork Session** (Edit button on a message): Creates a new session with history up to a specific edited message. Use this to explore different approaches from a particular point in the conversation.
    - **[Duplicate Session](/docs/guides/sessions/session-management#duplicate-sessions)** (Copy button in session list): Creates a complete copy of the entire session. Use this to preserve a working session or reuse its configuration.
    :::

  Queued messages appear as numbered cards showing the queue order. The first message in the queue is automatically sent when goose finishes each response.
  
  :::info Related Features
  - In general, pressing `Enter` while goose is processing a task queues the message, but clicking `Send` sends the task immediately and [interrupts the task](#interrupt-task)
  - When you type common interrupt keywords like "stop", "wait", or "hold on" in a queued message, goose pauses until you enter or send the next message and then continues processing the queue
  :::

  #### Queue Management Controls

  Queued messages run automatically in order as goose finishes each task, but you can manage the queue:
  - **Edit a message**: Click the message text to reveal the edit controls, then type your change and click `Save`
  - **Reorder messages**: Hover over the message card to reveal the <GripVertical className="inline" size={16} /> button, then grab it and drag the message up or down
  - **Send a message**: Click the <Send className="inline" size={16} /> button to send a message immediately and interrupt the current task
  - **Delete a message**: Click the <X className="inline" size={16} /> button to delete the message
  - **Clear the queue**: Click `Clear All` on the **Message Queue** card
  - **Collapse or expand the queue**: Click the <ChevronUp className="inline" size={16} /> or <ChevronDown className="inline" size={16} /> button on the **Message Queue** card

  #### Example Message Flow

  **Without queuing:**

  You send: "Can you refactor our authentication code to support OAuth 2.0 and add proper error handling? Also include unit tests for the OAuth flow, update the API documentation to reflect these changes, and create a migration script to help existing users transition to the new system."

  This approach might lead to overwhelming responses where important details get missed or tasks are handled superficially. Even sending a single prompt with clear sequential steps doesn't allow goose to focus on each task individually or build context progressively.

  **With queuing:**

  1. You send: "Refactor the authentication code to support OAuth 2.0"
  2. While goose is working, you queue the following messages:
     - "And add proper error handling"
     - "Add unit tests for the OAuth flow"
     - "Update the API documentation" 
     - "Create migration script for existing users"
  
  Each task builds on the previous one.

</TabItem>
<TabItem value="cli" label="goose CLI">
    Message queuing is not available in the goose CLI.
</TabItem>

    There are two ways to interrupt a task:

    #### Send interruption keyword
    1. Type a prompt that includes common interruption keywords like `stop`, `wait`, `hold on`, `actually`, or `instead`. Using keywords alone or at the beginning of sentences works best for reliable detection.
    2. Click `Send`
    
    goose stops processing the current task and asks for more information.
    
    #### Provide immediate redirection
    1. Type a prompt with more context and clarification or that changes direction. For example:
       - "I forgot to mention this is for a mobile app"
       - "Let's focus on React instead of TypeScript"
    2. Click `Send`
    
    goose stops processing the current task and pivots to the new request context.
    
    :::info Related features
    - Clicking `Send` while goose is processing a task interrupts the task but pressing `Enter` [queues the message](#queue-messages)
    - Typing a stop or pause keyword in a queued message also stops goose from processing the current task
    - You can also [edit a sent message](#edit-message) to provide more context and clarification or change direction during a session
    :::

    <details>
      <summary>Interruption Keywords List</summary>

      **High-priority keywords** (interrupt in any context):
      ```
      stop, halt, cease, quit, end, abort, cancel, wait, hold, pause, hold on, wait up, hold up
      ```

      **Medium-priority keywords** (interrupt only as exact matches or at beginning of sentences):
      ```
      no, nope, nah, wrong, incorrect, not right, actually, instead, rather, better idea, change of plans, nevermind, never mind, forget it, ignore that, disregard
      ```

      **Detection Rules**:
      - **Exact match** (100% confidence): Word/phrase matches exactly and always interrupts
      - **Beginning of sentence** (very high confidence): Word/phrase starts your message and always interrupts  
      - **Short messages only** (high confidence): In messages ≤20 characters, only high-priority keywords interrupt
      - **Case insensitive**: All detection is case-insensitive

      **Examples**:
      - ✅ "stop" interrupts (exact match)
      - ✅ "Wait, I meant something else" interrupts (beginning of sentence)
      - ✅ "no" interrupts (short message, high-priority)
      - ❌ "actually" in short message doesn't interrupt (medium-priority in short message)
      - ✅ "Actually, let's try React instead" interrupts (beginning of sentence)

    </details>

</TabItem>
<TabItem value="cli" label="goose CLI">
    1. Press `Ctrl+C` to interrupt the current task
    2. Type your prompt that provides more context or changes direction  
    3. Press `Enter`

    goose responds contextually to your new request.
    
</TabItem>

To use voice dictation:
    1. Click your chat session under `Chat` in the sidebar
    2. Click the microphone button on the right of the chat box and begin speaking
    3. To send your message, do one of the following:
       - Say "submit" to send the message and continue recording your next one. To stop recording, click the microphone button.
       - Click the microphone button to stop recording, then click `Send` or press `Enter`. This option allows you to edit the message before sending.
    
    The first time you use voice dictation, goose will request access to your microphone. While recording, you'll see `Listening` and `Transcribing` status indicators. goose transcribes your speech during natural pauses and adds the text to the chat box. 

    **If you don't see the microphone**, check the [models you have configured](/docs/getting-started/providers.md). For example, using OpenAI as the voice dictation provider requires that you have an OpenAI model configured in goose, even if using another LLM provider for chat.

   #### Important Notes
    * You can record up to 50MB of audio
    * ElevenLabs, Groq, and OpenAI send audio recordings to their servers for processing. The local provider processes audio entirely on your device—no data leaves your computer.
    * Voice input is appended to any existing text in the text input field
    * Recordings are not stored locally after transcription
    * To disable voice dictation, select `Disabled` from the provider dropdown

</TabItem>
<TabItem value="cli" label="goose CLI">
    Spellcheck is not available in the goose CLI.
</TabItem>

    1. **Drag and Drop**: Simply drag files from your computer's file explorer/finder and drop them anywhere in the chat window. The file paths will be automatically added to your message.

    2. **File Browser**: Click the <Paperclip className="inline" size={16} /> button at the bottom of the app to open your system's file browser and select files

    3. **Manual Path**: Type or paste the file path directly into the chat input

    4. **Quick File Search**: Use the [`@` shortcut key](/docs/guides/file-management#quick-file-search-in-goose-desktop) to quickly find and include files
</TabItem>
<TabItem value="cli" label="goose CLI">
    You can reference files by their paths directly in your messages. Since you're already in a terminal, you can use standard shell commands to help with file paths:

    ```bash
    # Reference a specific file
    What does this code do? ./src/main.rs

    # Use tab completion
    Can you explain the function in ./src/lib<tab>

    # Use shell expansion
    Review these test files: ./tests/*.rs
    ```
</TabItem>