[Requests and ideas] Feels solid to use so far, but the automatic tool call option needs a whiteli...
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
**Mood:** 😊
**Category:** Requests and ideas
Feels solid to use so far, but the automatic tool call option needs a whitelist option - similar to the VS code plugin. This allows for automations, restrictions on writes etc to protect projects.
Mostly this comes into the picture as writes and pushes are often something a developer will want to validate, but purely allowing all tool calls is not granular enough for that.
Cheers!
---
| Field | Value |
| --- | --- |
| App version | 0.2.29 |
| OS | Windows 10.0.26100 |
| Theme | GitHub |
| Path | /workflows |
| Tenure | Day 3 (Week 1) |
Contributor guide
Research direction
The issue does not name files, tests, or entry points. Start by locating the automatic tool call option and comparing it with the VS Code plugin's whitelist behavior; done means users can restrict tool calls granularly, especially writes and pushes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, vscode
- Domain
- authorization, desktop, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100