Blocks as Context
Attach blocks from your terminal as context so Warp’s Agent can understand errors, outputs, or previous commands when responding to your queries.
Attaching blocks as context
Warp’s Agent can use blocks from your Agent conversations as context to better understand your queries and generate more relevant responses.
You can attach a block directly from the terminal blocklist by clicking the AI sparkles icon on it and selecting “Attach as context.”
The most common use case is to ask the AI to fix an error. You can attach the error in a query to Agent Mode and type "fix it."
If you're already in Agent Mode, use the following ways to attach or clear context from your query:
Attach a previous block
To attach blocks to a query, you can use
CMD-UPto attach the previous block as context to the query. While holdingCMD, you can then use yourUP/DOWNkeys to pick another block to attach.You may also use your mouse to attach blocks in your session. Hold
CMDas you click on other blocks to extend your block selection.
Clear a previous block
To clear blocks from a query, you can use
CMD-DOWNuntil the blocks are removed from context.You may also use your mouse to clear blocks in your session. Hold
CMDas you click on an attached block to clear it.
When using "Pin to the top" Input Position, the direction for attaching or detaching is reversed (i.e. CMD-DOWN attaches blocks to context, while CMD-UP clears blocks from context).
Attach a previous block
To attach blocks to a query, you can use
CTRL-UPto attach the previous block as context to the query. While holdingCTRL, you can then use yourUP/DOWNkeys to pick another block to attach.You may also use your mouse to select blocks in your session. Hold
CTRLas you click on other blocks to extend your block selection.
Clear a previous block
To clear blocks from a query, you can use
CTRL-DOWNuntil the blocks are removed from context.You may also use your mouse to clear blocks in your session. Hold
CTRLas you click on an attached block to clear it.
When using "Pin to the top" Input Position, the direction for attaching or detaching is reversed (i.e. CTRL-DOWN attaches blocks to context, while CTRL-UP clears blocks from context).
Attach a previous block
To attach blocks to a query, you can use
CTRL-UPto attach the previous block as context to the query. While holdingCTRL, you can then use yourUP/DOWNkeys to pick another block to attach.You may also use your mouse to select blocks in your session. Hold
CTRLas you click on other blocks to extend your block selection.
Clear a previous block
To clear blocks from a query, you can use
CTRL-DOWNuntil the blocks are removed from context.You may also use your mouse to clear blocks in your session. Hold
CTRLas you click on an attached block to clear it.
When using "Pin to the top" Input Position, the direction for attaching or detaching is reversed (i.e. CTRL-DOWN attaches blocks to context, while CTRL-UP clears blocks from context).
Block visibility across views
Blocks in Warp belong to either the terminal view or a specific agent conversation:
Terminal blocks - Commands you run directly in the terminal. These always appear in your terminal blocklist and can be attached as context to multiple conversations.
Agent conversation blocks - Commands executed within an agent conversation (either by you or the agent). These only appear within that specific conversation and don't clutter your terminal blocklist.
This separation keeps your terminal view clean while preserving full context within each conversation.
Automatic context in agent conversations
When you're working inside an agent conversation, any shell commands you run are automatically included as context for your next query. This means you can:
Run a command to see its output
Ask the agent about the results without manually attaching the block
For example, in an agent conversation, run npm test and then ask "why did these tests fail?"—the test output is already part of the conversation context.
You can also manually attach terminal view blocks to add additional context from commands you ran outside the conversation.
Pending and attached context
When you select blocks in terminal view and start a new conversation, those blocks become pending context:
Pending context - Blocks are selected but the conversation hasn't started yet. If you deselect the blocks (
ESCorCMD-Kon macOS,ESCorCTRL-Kon Windows/Linux), they're removed from the agent view.Attached context - Once you submit your first query, the pending blocks become attached to the conversation and remain part of the context.
Last updated
Was this helpful?