feat: Capture command output + expose to new `atuin_output` tool (#3510)

1 files changed, 7 insertions, 1 deletions

diff --git a/docs/docs/ai/settings.md b/docs/docs/ai/settings.md
index a8d3dab3..edc54aaf 100644
--- a/docs/docs/ai/settings.md
+++ b/docs/docs/ai/settings.md
@@ -1,6 +1,6 @@
 # AI Settings
 
-All the settings that control the behavior of [Atuin AI](./introduction.md) are specified in an `[ai]` section in your `config.toml`. See [the configuration documentation](../../configuration/config/) for more detailed information about Atuin's configuration system.
+All the settings that control the behavior of [Atuin AI](./introduction.md) are specified in an `[ai]` section in your `config.toml`. See [the configuration documentation](../configuration/config.md) for more detailed information about Atuin's configuration system.
 
 ### enabled
 
@@ -42,6 +42,12 @@ Default: `true`
 
 Whether or not to include the "history search" capability in the context sent to the LLM. This allows the AI to request to search your Atuin history for relevant commands when generating suggestions or answering questions.
 
+### enable_history_output
+
+Default: `true`
+
+Whether or not to include the "history output" capability in the context sent to the LLM. This allows the AI to request to view the output of previous commands. This requires the [pty-proxy](../reference/pty-proxy.md) and [daemon](../reference/daemon.md) to be enabled and running in order for Atuin to capture commands' outputs.
+
 ### enable_file_tools
 
 Default: `true`