Skip to content

feat: add permission case system with required context for write/patc…#3392

Open
jmikedupont2 wants to merge 2 commits into
tailcallhq:mainfrom
meta-introspector:feature/permissions-display
Open

feat: add permission case system with required context for write/patc…#3392
jmikedupont2 wants to merge 2 commits into
tailcallhq:mainfrom
meta-introspector:feature/permissions-display

Conversation

@jmikedupont2
Copy link
Copy Markdown

…h operations

  • Add required context field to FSWrite, FSPatch, FSMultiPatch tool calls LLM must provide a justification for every write/patch/multipatch operation
  • Introduce PermissionCase struct for judicial-style evidence collection
  • Show proposed content/diff before TUI permission prompt
  • Include caller context (explanation) in the case panel
  • Update tool descriptions JSON schema with context field
  • Fix nixpkgs lock for required rustc 1.94+
  • Update all snapshot tests for new schema

…h operations

- Add required context field to FSWrite, FSPatch, FSMultiPatch tool calls
  LLM must provide a justification for every write/patch/multipatch operation
- Introduce PermissionCase struct for judicial-style evidence collection
- Show proposed content/diff before TUI permission prompt
- Include caller context (explanation) in the case panel
- Update tool descriptions JSON schema with context field
- Fix nixpkgs lock for required rustc 1.94+
- Update all snapshot tests for new schema
@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


mike dupont seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@github-actions github-actions Bot added the type: feature Brand new functionality, features, pages, workflows, endpoints, etc. label May 25, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 5, 2026

Action required: PR inactive for 5 days.
Status update or closure in 10 days.

@github-actions github-actions Bot added the state: inactive No current action needed/possible; issue fixed, out of scope, or superseded. label Jun 5, 2026
I see the issue - all these tests are using the old struct-based API with `.default()` and setters. Since we changed to an enum-based design, these tests need to be completely rewritten. Let me replace all the problematic tests:
````
**Update:** `crates/forge_domain/src/compact/summary.rs`
**MCP:** `patch`
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This is a regression

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Yes sorry I haven't actually spent any more time on this I only had the most basic stuff working I still use it a little bit do you want me to send you up the new version I have the basic permissions working it's not great though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

state: inactive No current action needed/possible; issue fixed, out of scope, or superseded. type: feature Brand new functionality, features, pages, workflows, endpoints, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants