Agent

The agent panel brings the coding agent you already use into Request Eagle: Claude Code, Codex or OpenCode. Point at what you mean in a request or its response, or mention a saved request or flow, ask about it, and let the agent read your code and run, fix or create saved requests and flows. The agent keeps its own sign-in, models and tools.

Open the panel

Click Agent in the status bar, or press Ctrl+Shift+I (Command+Shift+I on macOS). The panel runs the first agent it finds on your computer that is turned on in Settings > Agents; pick another from the menu at its top. In the panel, Ctrl+/ (Command+/ on macOS) opens the model menu, and Ctrl+N in the message box starts a new thread. Change any of these in Settings > Keybindings. Install an agent if none is found:

Sign in to the agent in a terminal first, the way you use it there. When an agent asks to sign in, the panel says how.

Cite what you mean

Select text in the URL, the request body, a script or the response, and press Ctrl+L (Command+L on macOS), or right-click it and choose Add to Agent. The selection appears as a cite in your message, where the caret is, named after what it quotes, such as Response body · L3–4. Without a selection, the field with focus is cited whole; the button with sparkles in the response toolbar cites the response. Click a cite to go back to its tab.

The agent reads each cite with where it comes from: the request, the response status, the lines, and the file the request is saved in. Variables such as {{token}} are cited as written, not filled in. A tab’s changes that are not saved yet are in its cites, and the agent is told they are not in the file.

Mention requests and flows

Type @ in your message to mention a saved request, flow or collection. Keep typing to narrow the list by name, or by a request’s method, URL or folder. Pick one with the arrow keys and Enter or Tab, or click it; Escape closes the list and keeps what you typed. The mention appears in your message named after what it mentions, such as Get user. Click it to open it.

The agent reads each mention with what it is, its collection and folder, and the file it is saved in, so it can read, run or edit it. A mention is of what is saved: changes in a tab that are not saved yet are not in the file. Cite them to show them to the agent.

What the agent can do

The agent works in the Git repository of the collection in the active tab, so it can read the code that serves your API, or else in Request Eagle’s own folder. It sees your saved collections and flows either way. With the Request Eagle CLI installed, it lists, edits and runs saved requests and flows through it; otherwise it edits their files.

The agent runs commands and changes files without asking: it starts in its own mode for that, such as Claude Code’s Bypass permissions or Codex’s Full access, and the panel allows anything it asks about anyway. To approve each step instead, turn on Ask before running tools for the agent in Settings > Agents, or pick another mode from the menu under the message. The other menus there show the exact model and reasoning level the agent runs with, and change them. When an agent leaves either to itself, the panel picks the model its default stands for and medium reasoning, or the first level the model offers without medium. Type in an open menu to filter it, and use the arrow keys and Enter to choose.

After each of the agent’s turns, Request Eagle reads collections and flows again. Requests and flows the agent added show in the sidebar, and open tabs without unsaved changes show the agent’s edits. Tabs with unsaved changes keep them, and saving asks whose changes to keep.

New Thread at the top of the panel starts over with a fresh agent.

Agent settings

Settings > Agents, or the gear at the top of the panel, lists each agent with its version and whether it is ready, signed out or not installed. Check Again starts each agent once to find out. For each agent you can:

• Turn it off, so the panel does not offer it.
• Ask before it runs tools, as above.
• Replace the Command that starts it, such as with an adapter you installed globally.
• Move its Config folder, where it keeps its settings and sign-in, to use another account.
• Add Variables it runs with, such as an API key or a base URL. Their values are saved in macOS Keychain, Windows Credential Manager or your desktop keyring.
• Choose which of its Models the model menu lists, and in which order.

Things to know

• Request Eagle talks to agents through the Agent Client Protocol. Claude Code and Codex speak it through adapters that npx downloads the first time, so the first thread takes longer to start.
• Request Eagle finds agents on the PATH of your login shell, as a terminal would, also when you open the app from the Dock or a launcher.
• What you cite and ask goes to the agent’s model provider, like anything you send the agent in a terminal.
• A very long cite, such as a large response, is cut in the message; the agent gets a file with all of it.