Skip to content

Conversation

@yingjiehe-xyz
Copy link
Contributor

@yingjiehe-xyz yingjiehe-xyz commented Mar 10, 2025

Enable smart approve for user by default and no need the experiment control

Test:
image

@yingjiehe-xyz yingjiehe-xyz marked this pull request as ready for review March 10, 2025 20:59
@yingjiehe-xyz yingjiehe-xyz changed the title feat: allow user to enable/disable smart approve feat: enable smart approve for user by default Mar 10, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Mar 10, 2025

PR Preview Action v1.6.0

🚀 View preview at
https://block.github.io/goose/pr-preview/pr-1599/

Built to branch gh-pages at 2025-03-10 23:58 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

:::

</TabItem>
</Tabs>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could we keep a note here explaining 'Read Write approve' -

goose will only ask for permission before tool call for tools that it deems are 'write' tools, for example any 'text editor write', 'text editor edit', 'bash - rm, cp, mv' commands, as an example. Read write approval makes best effort attempt at classifying read or write tools- this is interpreted by your LLM provider. 

value: 'approve',
label: 'Approval needed',
description: 'Editing, creating, and deleting files will require human approval.',
description:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'Classifies the tool as either a read-only tool or write tool. Write tools will ask for human approval'

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sg, done

Copy link

@wendytang wendytang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would still prefer to veer away from 'smart' 'intelligent' - the truth is we are just asking for write permission. If it were truly learned, then we could call it 'smart', but there is no learning here

@yingjiehe-xyz
Copy link
Contributor Author

I would still prefer to veer away from 'smart' 'intelligent' - the truth is we are just asking for write permission. If it were truly learned, then we could call it 'smart', but there is no learning here

make sense, refresh the doc

Copy link

@wendytang wendytang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@yingjiehe-xyz yingjiehe-xyz merged commit 9447b79 into main Mar 11, 2025
8 checks passed
@yingjiehe-xyz yingjiehe-xyz deleted the yingjiehe/ui branch March 11, 2025 00:57
michaelneale added a commit that referenced this pull request Mar 11, 2025
* main:
  feat: enable smart approve for user by default (#1599)
  ui: fix modal state (#1598)
  ui: setting configuration (#1597)
  fix: merge error logging in goose bench  (#1545)
  feat: add additional goosebench evals (#1571)
  chore: update types and imports (#1594)
  Retain session through view changes (#1580)
  docs: Add steps for desktop tutorial (#1590)
  remove env vars from bottom menu model setting (#1584)
  Fix Goosehints modal UI (#1581)
  docs: typo fix (#1593)
  feat: update config endpoints for use with providers (#1563)
  fix: update anthropic provider headers (#1592)
  feat: Build Goose in a Docker Container (#1551)
  docs: voyp blog post (#1588)
sheagcraig added a commit to sheagcraig/goose that referenced this pull request Mar 11, 2025
* upstream/main: (48 commits)
  feat: enable smart approve for user by default (block#1599)
  ui: fix modal state (block#1598)
  ui: setting configuration (block#1597)
  fix: merge error logging in goose bench  (block#1545)
  feat: add additional goosebench evals (block#1571)
  chore: update types and imports (block#1594)
  Retain session through view changes (block#1580)
  docs: Add steps for desktop tutorial (block#1590)
  remove env vars from bottom menu model setting (block#1584)
  Fix Goosehints modal UI (block#1581)
  docs: typo fix (block#1593)
  feat: update config endpoints for use with providers (block#1563)
  fix: update anthropic provider headers (block#1592)
  feat: Build Goose in a Docker Container (block#1551)
  docs: voyp blog post (block#1588)
  fix: included files was panicing because dir didnt exist (block#1583)
  feat: work with docs/xls and simple html (block#1526)
  feat: parallel processing in approve mode (block#1575)
  Feat: support auto-including dirs in binary/bench-work-dir (block#1576)
  refactor models component (block#1535)
  ...
cbruyndoncx pushed a commit to cbruyndoncx/goose that referenced this pull request Jul 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants