SDK Prompting for permissions to read an output file created by CLI for large outputs

Closed
#1,077 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
50/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Domain
authorization, cli

Research direction

Start by tracing the CLI large-output handling from the point where the output is saved to a temporary file and the SDK forwards a read permission request to the client. Done means reads of these CLI-created output files are automatically approved without an additional client permission prompt.

Written by the indexing model from the issue text.

Description

vs-code
Image 
{"type":"tool.execution_complete","data":{"toolCallId":"call_Gy2uDhKI9qIX2yMRS5USIm3C","....,"result":{"content":"Output too large to read at once (74.5 KB). Saved to: /var/folders/tk/xz6l8fxs0cxgphyh0xy2n4hh0000gn/T/copilot-tool-output-1776206629188-gotvti.txt\nConsider using tools like grep (for [\"ts\",\"js\",\"json\"]","matches_found":"true","large_output":"true","large_output_file":"/var/folders/tk/xz6l8fxs0cxgphyh0xy2n4hh0000gn/T/copilot-tool-output-1776206629188-gotvti.txt"},"

& then SDK passes permission request onto client to read this file.
CLI should auto approve such reads.

Dominant language
Java
Stars
10.5k
Forks
1.5k
Avg merge
1d 12h
Merged PRs (30d)
133

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/copilot-sdk

All issues in github/copilot-sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.