-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Document recipe slash commands feature #6075
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
|
||
| To run the recipe, type your custom command with a leading slash into any goose chat session: | ||
| ``` | ||
| /run-tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we show an in progress session like how we usually do here.
Context: ○○○○○○○○○○ 0% (0/200000 tokens)
( O)> /run-tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those instructions apply to both Desktop and CLI
| </TabItem> | ||
| </Tabs> | ||
|
|
||
| To run the recipe, type your custom command with a leading slash into any goose chat session: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how do you run it in desktop or is it only possible to run in cli because it's a command? I thought you could run these in desktop too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah for both versions you just type /command-name into the chat. That's also why I don't have the CLI session decorations (context and tokens) shown in the example, just the "prompt"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you write out the instructions more explicitly for goose desktop and cli..so it's more obvious. sorry..but like if im this dumb, their may be someone just as dumb as me lolol.
Just do like the tabs..and do the start new session steps and then have them type the /command in..number the steps. please and thank you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're not dumb!!! But yes I will make it totally explicit 😂
…erer * origin/main: (26 commits) Don't persist ephemeral extensions when resuming sessions (#5974) chore(deps): bump mdast-util-to-hast from 13.2.0 to 13.2.1 in /ui/desktop (#5939) chore(deps): bump node-forge from 1.3.1 to 1.3.2 in /documentation (#5898) Add Scorecard supply-chain security workflow (#5810) Don't show subagent tool when we're a subagent (#6125) Fix keyboard shortcut conflict for Focus Goose Window (#5809) feat(goose-cli): add feature to disable update (#5886) workflow: enable docs-update-recipe-ref (#6132) fix: filter tools in Ollama streaming when chat mode is enabled (#6118) feat(mcp): platform extension for "code mode" MCP tool calling (#6030) workflow: auto-update recipe-reference on release (#5988) Document recipe slash commands feature (#6075) docs: add GitHub Copilot device flow authentication details (#6123) Disallow subagents with no extensions (#5825) chore(deps): bump js-yaml in /documentation (#6093) feat: external goosed server (#5978) fix: Make datetime info message more explicit to prevent LLM confusion about current year (#6101) refactor: unify subagent and subrecipe tools into single tool (#5893) goose repo is too big for the issue solver workflow worker (#6099) fix: use system not developer role in db (#6098) ...
Summary
Document the new recipe slash commands feature (#5718 )
session-recipes.mdgoose-cli-commands.md/summarizecommand with/compactType of Change
AI Assistance