From 4ff383aa13f29485725d48601f30fb74de5b8311 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Erik=20Bj=C3=A4reholt?= <erik@bjareho.lt>
Date: Sun, 8 Dec 2024 18:37:49 +0100
Subject: [PATCH] docs: moved usage rubrics from example.rst to usage.rst

---
 docs/examples.rst | 29 -----------------------------
 docs/usage.rst    | 33 +++++++++++++++++++++++++++++++++
 2 files changed, 33 insertions(+), 29 deletions(-)

diff --git a/docs/examples.rst b/docs/examples.rst
index 1bf73954..5e38711c 100644
--- a/docs/examples.rst
+++ b/docs/examples.rst
@@ -50,32 +50,3 @@ Do you have a cool example? Share it with us in the `Discussions <https://github
    demos
    automation
    projects
-
-
-.. rubric:: Skip confirmation prompts
-
-You can skip confirmation prompts using the ``--no-confirm`` flag. This is useful when you are confident the LLM will do what you want, so you don't want to have to confirm actions:
-
-.. code-block:: bash
-
-    gptme --no-confirm 'create a snake game using curses in snake.py, dont run it'
-
-.. rubric:: Multiprompt syntax
-
-The ``-`` separator allows you to chain multiple prompts together, letting the assistant finish running tools for one prompt before moving to the next:
-
-.. code-block:: bash
-
-    gptme 'create a project' '-' 'add tests' '-' 'commit changes'
-
-This is particularly useful for breaking down complex tasks into steps and creating :doc:`automation` workflows.
-
-.. rubric:: Non-interactive mode
-
-The ``--non-interactive`` flag runs gptme in a mode that terminates after completing all prompts. This is useful for scripting and automation:
-
-.. code-block:: bash
-
-    gptme --non-interactive 'create a snake game using curses in snake.py, dont run it' '-' 'make the snake green and the apple red'
-
-Note: ``--non-interactive`` implies ``--no-confirm``, so you don't need to specify both.
diff --git a/docs/usage.rst b/docs/usage.rst
index ba574589..7622d582 100644
--- a/docs/usage.rst
+++ b/docs/usage.rst
@@ -71,6 +71,35 @@ You can start chats and request changes directly from the command line. The cont
 
 With the :ref:`tools:browser` extras installed, the assistant can process URLs included in the prompt and interact with web content.
 
+.. rubric:: Multiprompt syntax
+
+The ``-`` separator allows you to chain multiple prompts together, letting the assistant finish running tools for one prompt before moving to the next:
+
+.. code-block:: bash
+
+    gptme 'create a project' '-' 'add tests' '-' 'commit changes'
+
+This is particularly useful for breaking down complex tasks into steps and creating :doc:`automation` workflows.
+
+.. rubric:: Skip confirmation prompts
+
+You can skip confirmation prompts using the ``--no-confirm`` flag. This is useful when you are confident the LLM will do what you want, so you don't want to have to confirm actions:
+
+.. code-block:: bash
+
+    gptme --no-confirm 'create a snake game using curses in snake.py, dont run it'
+
+.. rubric:: Non-interactive mode
+
+The ``--non-interactive`` flag runs gptme in a mode that terminates after completing all prompts. This is useful for scripting and automation:
+
+.. code-block:: bash
+
+    gptme --non-interactive 'create a snake game using curses in snake.py, dont run it' '-' 'make the snake green and the apple red'
+
+Note: ``--non-interactive`` implies ``--no-confirm``, so you don't need to specify both.
+
+
 Commands
 --------
 
@@ -102,3 +131,7 @@ For more detailed information about specific features, check out:
 - :doc:`tools` - Available tools and their usage
 - :doc:`providers` - Supported LLM providers
 - :doc:`server` - Web UI and API server setup
+
+-----
+
+For further usage examples, see the :doc:`examples` page.