docs: sessions reorg and conversation features #4462
Conversation
|
| title="Conversing with Goose" | ||
| description="Discover features you can use to share information and communicate with Goose during sessions." | ||
| link="/docs/guides/sessions/conversing-with-goose" | ||
| /> |
There was a problem hiding this comment.
should we move context management in here?
There was a problem hiding this comment.
Will do! I had thought it might be more discoverable where it is but I think that reasoning is probably unfounded
There was a problem hiding this comment.
But to confirm: I should move the topic into the Sessions node vs adding a card?
| <Card | ||
| title="AI Prompting 101: How to Get the Best Responses from Your AI Agent" | ||
| description="Make your sessions more effective by adding structure to your prompts." | ||
| link="/blog/2025/03/19/better-ai-prompting" |
There was a problem hiding this comment.
I think this blog could be added: /blog/2025/08/18/understanding-context-windows
| - You're using [voice dictation](#voice-dictation) and need to capture thoughts quickly | ||
|
|
||
| :::tip | ||
| Goose may perform better when complex tasks are handled in stages. A structured approach can both improve accuracy and give you more control over the process. |
There was a problem hiding this comment.
This approach of breaking complex tasks into stages is actually called prompt chaining . I wonder if it's worth using that phrase and linking to this. Make us sound even smarter.
| Queued messages appear as numbered cards showing the queue order. The first queued message is automatically sent when Goose finishes each response. | ||
|
|
||
| :::info Related Features | ||
| - Pressing `Enter` while Goose is processing a task queues the message, but clicking `Send` sends the task immediately and [interrupts the task](#interrupt-task) |
There was a problem hiding this comment.
Interesting..Imma have to try to use this and see what the user experience is because in my opinion..I would get confused with how to queue a message and interrupt a task..like I get it in theory, but curious if I would feel comfy implementing it . I feel like I need a message queue mode or something like that because I always press the enter button by accident. Let's ask this question in the team meeting.
However, I do like the idea of queue-ing up a message.
There was a problem hiding this comment.
yeah you do need to be deliberate but it wasn't too hard to adjust. If you hit Enter instead of Send, you can Send Now from the queue. Goose confirmed it seems to be intentional in the code
But maybe something like Cmd+Send or Cmd+Enter would be easier
There was a problem hiding this comment.
This comment isn't outdated, I just added edited in the vicinity (added "(or interrupts if using interruption keywords)" to Press Enter step)
Co-authored-by: Rizel Scarlett <rizel@squareup.com>
Co-authored-by: Rizel Scarlett <rizel@squareup.com>
…pt keyword in queue
|
another question @dianed-square ..what do you think of these titles for the sidebars Managing Sessions/ |
|
@blackgirlbytes I changed the topic titles to match the sidebar, let me know if you want me to revert that change |
It looks like it failed to deploy |
|
AMAZING work! |
|
Thanks @blackgirlbytes ! But I think we're only using h4s in tabbed content because the in-topic links only work for active tabs. If that jibes with your understanding, I'll revert that change |
|
ohhh okay yes..revert the change. my apologies @dianed-square |
Co-authored-by: Rizel Scarlett <rizel@squareup.com> Signed-off-by: Carine Bruyndoncx <bruyndoncx@gmail.com>
* main: Align Dynamic Task Interface with Recipe Interface (#4311) docs: copilot auth and mcp-ui links (#4497) docs: July and August 2025 Community All-Stars Update (#4501) remove clicking outside to close recipe warning (#4502) lower min width to 450 for small screens Convert recipe create and import forms to use tanstack form and zod schema validation (#4499) Repo CI: use a writable location for Goose home directory (#4500) feat: Add functionality to delete session in history list view (#4480) fix: recipe deeplink "+" characters and folder change (#4471) Add session to agents (#4216) fix: need to send errors to appropriate stream (#4491) Add Docker support for Goose in CI/CD pipelines (#4434) Add visual indicator while recipe loads (#4447) Disable chat input while extensions load (#4417) chore(release): release version 1.7.0 (#4391) fix double filtering (#4409) Rewrite the developer mcp using the rmcp sdk (#4297) docs: sessions reorg and conversation features (#4462)
Co-authored-by: Rizel Scarlett <rizel@squareup.com> Signed-off-by: Matt Donovan <mattddonovan@protonmail.com>
Co-authored-by: Rizel Scarlett <rizel@squareup.com> Signed-off-by: HikaruEgashira <hikaru-egashira@c-fo.com>
Pull Request Description
Add Sessions node with new Conversing with Goose topic, remove two sections from Managing Goose Sessions.
Note: I saw no difference in the interrupt behavior for stop/pause keywords in testing or visual indicators.
documentation/docs/guides/sessions/_category_.jsonanddocumentation/docs/guides/sessions/index.md:documentation/docs/guides/sessions/conversing-with-goose.md:documentation/docs/guides/sessions/managing-goose-sessions.md:documentation/docs/guides/smart-context-management.md:Add redirect and update links:
documentation/docs/guides/recipes/session-recipes.mddocumentation/docs/guides/tips.mddocumentation/docs/quickstart.mddocumentation/docusaurus.config.tsUpdate sidebar position to persist current order:
documentation/docs/guides/goose-permissions.mddocumentation/docs/guides/handling-llm-rate-limits-with-goose.mddocumentation/docs/guides/interactive-chat/_category_.jsondocumentation/docs/guides/managing-projects.mddocumentation/docs/guides/managing-tools/_category_.jsondocumentation/docs/guides/recipes/_category_.jsondocumentation/docs/guides/updating-goose.mddocumentation/docs/guides/using-goosehints.md