From 5cf7267fc29b719c631031eed2a7fd48bd0b5ae3 Mon Sep 17 00:00:00 2001 From: broodling-bot Date: Tue, 17 Feb 2026 19:52:12 +0000 Subject: [PATCH 1/2] docs: add background execution guidance for session auth --- LLM_USAGE.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/LLM_USAGE.md b/LLM_USAGE.md index bf3d290..7a407e9 100644 --- a/LLM_USAGE.md +++ b/LLM_USAGE.md @@ -145,6 +145,17 @@ JSON output: 2. Ask them to open it in their browser and authorize 3. The command waits automatically and stores the session when authorized (up to 6 minutes) +#### Background Execution + +The `session auth` command blocks for up to 6 minutes while waiting for the user to authorize in the browser. To avoid blocking your main thread, run it as a background process: + +1. Start `session auth` in the background +2. Capture and display the `short_url` / `authorization_url` to the user immediately +3. Poll the process for completion +4. Once it exits successfully, verify with `controller session status --json` + +This keeps the agent responsive to other user requests while waiting for authorization. + ### 3. Execute Transaction **Single call (positional args: contract, entrypoint, calldata):** From a1820d7e62a33d22651ef0e92c62bb28db3f0649 Mon Sep 17 00:00:00 2001 From: broodling-bot Date: Tue, 17 Feb 2026 19:54:21 +0000 Subject: [PATCH 2/2] docs: prefer short_url over authorization_url --- LLM_USAGE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/LLM_USAGE.md b/LLM_USAGE.md index 7a407e9..3ce34c3 100644 --- a/LLM_USAGE.md +++ b/LLM_USAGE.md @@ -150,7 +150,7 @@ JSON output: The `session auth` command blocks for up to 6 minutes while waiting for the user to authorize in the browser. To avoid blocking your main thread, run it as a background process: 1. Start `session auth` in the background -2. Capture and display the `short_url` / `authorization_url` to the user immediately +2. Capture and display the `short_url` to the user immediately (fall back to `authorization_url` if unavailable) 3. Poll the process for completion 4. Once it exits successfully, verify with `controller session status --json`