Replies: 3 comments 1 reply
-
|
will take a look @mNantern |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I've tested again with nono v0.42.0 and I see a better outcome for the proxy: And with As for the keyring I have the same issue: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hey @lukehinds, I'm facing the same issue (as @mNantern ) with injection custom proxy credentials (Nono Version: 0.40.0). Config: Command (run inside sandbox): Output: Verbose Logs: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm currently experimenting with an headless VM (Debian 13 with Lima) and nono to execute an AI agent with full permission (including root on the VM).
I'm using nono for it's proxy and credentials injection (currently with headless keyring).
This is my current configuration:
{ "extends": "claude-code", "meta": { "name": "claude-code-locked", "version": "1.0.0", "description": "Claude Code locked" }, "network": { "network_profile": null, "credentials": ["gitlab"], "allow_domain": [ "api.anthropic.com", "platform.claude.com", "gitlab.mysite.com", "galaxy.ansible.com", "ansible-galaxy-ng.s3.dualstack.us-east-1.amazonaws.com" ], "custom_credentials": { "gitlab": { "upstream": "https://gitlab.mysite.com", "credential_key": "gitlab_token", "env_var": "GITLAB_TOKEN", "inject_header": "Authorization", "credential_format": "Bearer {}" } } } }I think that I have an issue with my config because I can easily bypass the proxy:
Without
noproxy:And same with the keyring, I can access the secret from inside nono:
What I am doing wrong?
Beta Was this translation helpful? Give feedback.
All reactions