-
Notifications
You must be signed in to change notification settings - Fork 227
feat: cost confirmation flows #21
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sweatybridge
approved these changes
Apr 5, 2025
sweatybridge
reviewed
Apr 6, 2025
Co-authored-by: Han Qiao <[email protected]>
Co-authored-by: Han Qiao <[email protected]>
Co-authored-by: Han Qiao <[email protected]>
sweatybridge
approved these changes
Apr 6, 2025
GQAdonis
pushed a commit
to skytok-net/supabase-mcp
that referenced
this pull request
Aug 14, 2025
…/project-cost-prompt feat: cost confirmation flows
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We need to be crystal clear on which tools incur additional costs and we need users to confirm their understanding before running them. To do this we add two new tools:
get_cost
confirm_cost
Flow
The LLM calls
get_cost
to understand the cost of a new project or new branch (this will depend on the org plan and how many existing projects are in that org).The rules for new projects are:
create_project
will return an error)For new branches, cost is always $0.01344 / hour
The the LLM shares this information with the user, then calls
confirm_cost
which the user can choose to run.confirm_cost
returns a confirmation ID that is passed tocreate_project
orcreate_branch
. Bothcreate_project
orcreate_branch
require aconfirm_cost_id
and will not run without them.