[FEATURE]: Setting global permissions for custom tool #4881

Activity

1. JosXa

   added

   discussionUsed for feature requests, proposals, ideas, etc. Open discussionUsed for feature requests, proposals, ideas, etc. Open discussion

   on Nov 28, 2025
2. github-actions commented on Nov 28, 2025

   

   github-actionsBot

   on Nov 28, 2025 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • ShellFailed with exit code 1 when OpenCode tries to "ask" for permissions (Windows) #4880: ShellFailed with exit code 1 when OpenCode tries to "ask" for permissions - Similar issue with permission system not working as expected
   • Plan agent ignores permissions and always forbids file edits #3991: Plan agent ignores permissions and always forbids file edits - System prompts override permission settings
   • BUG: Overriding built-in agents, doesn't allow overriding permissions #3575: Overriding built-in agents, doesn't allow overriding permissions - Custom configuration not being respected for permissions
   • How to enable mcp tool approval dialog? #4854: How to enable mcp tool approval dialog? - Similar request for "ask" mode permissions on tools (for MCP tools)
   • Custom Agent Writes/Edits Files Despite Configuration Restrictions #3948: Custom Agent Writes/Edits Files Despite Configuration Restrictions - Custom agent ignoring permission configuration

   Feel free to ignore if none of these address your specific case.
3. rekram1-node commented on Dec 5, 2025

   

   rekram1-node

   on Dec 5, 2025

   Contributor

   More actions

   Yeah permissions only apply to a few tools rn we are gonna make them work w/ everything and w/ wildcards
4. rekram1-node

   self-assigned this

   on Dec 5, 2025
5. peltax commented on Mar 8, 2026

   

   peltax

   on Mar 8, 2026

   More actions

   For now you can add the permission check in custom tool itself:

   export default tool({
     description: "Ask a question",
     args: {
       query: tool.schema.string().describe("Search query")
     },
     async execute(args, ctx) {
       const q = encodeURIComponent(args.query);    
       await ctx.ask({
         permission: "mytoolname",
         patterns: [q],
         always: ["*"],
         metadata: {},
       })
      
       // at this point permission is already granted
   
6. nodiscc commented on Apr 21, 2026

   

   nodiscc

   on Apr 21, 2026

   More actions

   Still reproducible on v1.14.19

   Example working custom tool:

   $ cat ~/.config/opencode/tools/searxng.ts 
   import { tool } from "@opencode-ai/plugin"
   
   const SEARXNG_URL = "https://searx.example.org/search"
   
   export default tool({
     description: "Search the web using self-hosted SearXNG instance",
     args: {
       query: tool.schema.string().describe("Search query"),
       limit: tool.schema.number().optional().describe("Max number of results (default 10)"),
     },
   
       const limit = args.limit || 10
       const url = `${SEARXNG_URL}?q=${encodeURIComponent(args.query)}&format=json`
       const raw = await Bun.$`curl -k -s ${url}`.text()
       const data = JSON.parse(raw)
       const results = (data.results || []).slice(0, limit)
       return JSON.stringify(
         results.map((r) => ({
           title: r.title,
           url: r.url,
           engine: r.engine,
           content: r.content || "",
         })),
         null,
         2,
       )
     },
   })

   The tool always runs without asking for permission, for example when prompted with do a searxng search for "example topic"

   The workaround (adding await ctx.ask) mentioned by @peltax doesn't seem to work either, the tool still runs without asking for permission.
7. anjanpoonacha

   added a commit that references this issue on Apr 30, 2026

   fix(plugin): enable permission checks for custom tools

   ...

   This issue will close once commit 96a7ac1 is merged into the 'release' branch.

   96a7ac1
8. thdxr

   removed

   discussionUsed for feature requests, proposals, ideas, etc. Open discussionUsed for feature requests, proposals, ideas, etc. Open discussion

   on May 3, 2026
9. anjanpoonacha

   added a commit that references this issue on May 20, 2026

   fix(plugin): enable permission checks for custom tools

   ...

   This issue will close once commit 2b6eb74 is merged into the 'release' branch.

   2b6eb74
10. github-actions commented on Jul 3, 2026

    

    github-actionsBot

    on Jul 3, 2026 – with GitHub Actions

    Contributor

    More actions

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
11. github-actions

    closed this as not plannedon Jul 3, 2026