Make --files flag enabled by default with --no-files opt-out#262
Merged
Conversation
Filesystem access (read/write/run in the launch directory, sandboxed with write/run confirmation) is now on by default for the live voice agent; pass `--no-files` to opt out. Previously the agent silently ran against an empty in-memory filesystem unless `--files` was passed, so it would report the working directory as empty even when real files were present. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RQzGo8b3DKLg9aCYp9k32M
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Changes the
--filesoption for theassembly livecommand from opt-in (defaultFalse) to opt-out (defaultTrue), making filesystem access available to the agent by default.Changes
filesparameter inlive()command to default toTrueand use--files/--no-filesboolean flag syntax instead of just--files--no-filesdisables it--filesto demonstrating--no-files(the less common case)test_files_flag_resolves_into_options()to verify the flag behavior at the argv→options boundary, ensuring the default isn't silently mutatedImplementation details
The test uses
CliRunnerto invoke the command with different argv combinations ([],["--no-files"],["--files"]) and verifies that the resultingopts.filesvalue matches expectations. This pins the default at the CLI seam rather than relying on the Option default alone.https://claude.ai/code/session_01RQzGo8b3DKLg9aCYp9k32M