# Search, prompt bindings, and tool output

These settings tune what Gideon retrieves, which instructions serve a runtime context, and how large tool results enter its context.

## Search
Open **Settings → Search** to review available search providers and bindings. A search service may need an installed app and its connection. Test a small known query before assuming a saved selection works. Hosted credentials belong in Connections; model routing is managed.

## Prompt bindings
**Settings → Prompts** assigns a prompt to a runtime context. Edit its body on the Prompts page, then bind it here. Unset contexts use bundled defaults. Record why a custom prompt differs and test it with representative input.

## Tool-output projection
Open **Settings → Tool output** to configure how a large tool result is summarized into context. A custom rule has a name, a content-marker regular expression, and a projection strategy. Rules are checked before the built-in detection.

Use a real sample of the verbose output when creating a rule. Confirm that the retained preview includes the information needed for the task. The raw result should remain recoverable when more detail is needed; a compact preview is not the complete evidence.

## Keep changes narrow
A broad regex or prompt binding can affect many tasks. Change one rule at a time, try it on actual output, and keep the previous setting available while you assess the result.