Skip to content
Discussion options

You must be logged in to vote

There's no --block-cwd flag, but a profile can do it. The prompt only shows up when the CWD access requirement isn't None. With no profile it defaults to read, which is why you get asked. If you load a profile with workdir.access set to "none", there's nothing to request, so it should skip the prompt entirely:

{ "workdir": { "access": "none" } }

Save that as e.g. ~/.config/nono/profiles/no-cwd.json and run nono run --profile no-cwd -- yourtool. Every profile field has a default, so that one key should be enough. If you're extending another profile, setting workdir also overrides the inherited value.

Here's the logic in the source:

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@oxzidized
Comment options

Answer selected by oxzidized
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants