+ jHjuRt^RIHt^RIt^RIt^RIt^RIt^RIHt^RIH t H t ^RI H t ^RI Ht^RIHt^RIHt^R IHt^R IHtHtHtR R ltR RltRRltRRltRRltRRltRRlt RRlt!RRlt"RRlt#RR lt$R!R"lt%R#R$/R%R&llt&R'R(lt'R)R*lt(R+R,lt)R-R.lt*R/R0lt+R1R2lt,R3R4lt-R5R6lt.R7R8lt/R9R:lt0R;R<lt1R#)=z'CLI handlers for ``hermes egress ...``.) annotationsN)datetime)ListOptional)Console)Panel)Table) iron_proxy) mask_secret) load_configload_env save_configc V^8dQhRRRR/#) parent_parserzargparse.ArgumentParserreturnNone)formats"9/home/ubuntu/.hermes/hermes-agent/hermes_cli/proxy_cli.py __annotate__rs1'1' 71'D1'cVPRR7pRR\R\RRR73.3R R \R \\R R \ P R2R73R\RRR73R\RRR73R\RRR73R\RRR RR73R\RRRR73.3RR\.3R R!\.3RR"\.3R#R$\.3R%R&\R'\RR(R73.3R)R*\.3R+R,\.3. pVFHwr4rVVPW4R-7pVFwrVP!V3/V BK VP!VR.7KJ R #)/z5Attach the egress subcommand tree to a parent parser.egress_command)destinstallz'Install the PM-pinned iron-proxy binaryz--force store_truez"Verify and repair the managed copy)actionhelpsetupz=Interactive wizard: install + CA + mint tokens + write configz --tunnel-portNz"Override the tunnel port (default ))typedefaultrz--from-bitwardenuTreat secrets as managed by Bitwarden — discover provider keys from secrets.bitwarden config instead of the current env. Fails loudly if BW is unreachable rather than silently falling back.z--no-bitwardenz|Explicitly switch credential_source back to env on re-setup (only meaningful when the previous setup used --from-bitwarden).z--rotate-tokensuMint fresh proxy tokens for every provider (default is to preserve tokens for providers that already had one — avoids 401-ing already-running sandboxes on re-setup).z --restartrestartzIf a daemon is already running, restart it automatically after writing the new config/tokens (non-interactive default on a tty is to ask).)rrr"rz --no-restart store_falsez|Do not restart a running daemon after setup; you'll need to run `hermes egress restart` yourself for changes to take effect.)rrrstartzStart the managed iron-proxystopzStop the managed iron-proxyz ##F+BB/BG MM1&G9EF  7u=> WXs*A// B*:%B%%B*c V^8dQhRRRR/#rGr)rs"rrrVs! ! &! 3! rcv\4pVP\P!RRR74\ V4'g^#\ V4pVf^#\ W4pVf^#\WV.VO5!pVf^#\WV4VP4VPR4VPR4^#)z\Four-step wizard; each ``_setup_*`` phase prints its own step and returns ``None`` to abort.z[bold]iron-proxy setup[/bold] Routes outbound sandbox traffic through a local TLS-intercepting proxy so prompt-injected agents never see real provider API keys. [dim]Project: https://github.com/ironsh/iron-proxy (Apache-2.0)[/dim]cyan) border_styleu_[green]✓ iron-proxy is configured.[/green] Sandboxes will route outbound traffic through it.aO Start: [cyan]hermes egress start[/cyan] Restart: [cyan]hermes egress restart[/cyan] (after any re-setup) Reload: [cyan]hermes egress reload[/cyan] (apply ruleset edits in-place, no restart) Status: [cyan]hermes egress status[/cyan] Stop: [cyan]hermes egress stop[/cyan] Disable: [cyan]hermes egress disable[/cyan]) rrQrfit_setup_install_binary_setup_ca_cert_setup_mint_tokens_setup_write_config_setup_restart_daemon)rHrScamappings proxy_cfgs& rr/r/VsiG MM%)) Q  ! ) )  B z!'0H#G8AbAI'3 MMO MMst MM 8 rc V^8dQhRRRR/#)rrSrrrOr)rs"rrrzs  7 t rcn\V^R4\P!RR7pVf'VPR4\P!4p\P !V4;'gRpVPRV RV 24R # \ d!pTPR T R 24Rp?R#Rp?ii;i) zInstall the iron-proxy binaryFinstall_if_missingNu* No iron-proxy on PATH — downloading…rL [green]✓[/green] rMu [red]✗ install failed: [/red]T)_stepr1find_iron_proxyrQrNrRrP)rSrTrVrUs& rr\r\zs '156 ##u= > MMF G**,F''/FF3F -fXRyAB   3C5?@sAB -B B4B//B4cV^8dQhRR/#)rrSrr)rs"rrrsGrc\V^R4\P!4wrTP RT 24Y3# \d!pTP RT R24Rp?R#Rp?ii;i)rzGenerate a CA certu! [red]✗ CA generation failed: rjNri)rkr1ensure_ca_certrPrQ)rSca_crtca_keyrUs& rr]r]sm '1*+**, MM)&23 >  9#fEFs= A(A##A(c V^8dQhRRRR/#rrSrrHrIr)rs"rrrsBBB/ABrc &\V^R4.pVP'd\V4pVfR#M'\4pV'dVP RV R24\ P !T;'gRR7p\ P!4p\\VRR44pV'EdV'd\PP4'd5VP R4\R 4R 8wdVP R 4R#\ P!4pVR , pVP4'do\ P"!4P%R 4p VRV 2, p \&P(!\+V4\+V 44VP RV R24M!V'dV'gVP R4\ P.!WTVR7p V 'gYVP R4VP R4\1\ P24Fp VP RV 24K R#\ P4!T;'gRR7pV'dPVP 4VP R4VFpVP RV 24K VP R4VP \7V RRRR74V # \,d!p TP RT R24Rp ? EL6Rp ? ii;i)zVDiscover providers, merge with existing tokens (rotating on request), print the table.z%Mint proxy tokens for known providersNz [dim]Loaded z> provider key name(s) from ~/.hermes/.env for discovery.[/dim])available_env_names rotate_tokensFu[yellow]⚠[/yellow] --rotate-tokens will invalidate proxy tokens in every running Hermes sandbox. They will start 401-ing against upstreams until restarted.zType 'rotate' to confirm: rotatezellow]Cancelled.[/yellow]z mappings.jsonz %Y%m%dT%H%M%Szmappings.json.rotated-z [dim]backup: [/dim]z6 [yellow]Could not back up mappings before rotation: [/yellow]z_[dim]Note: --rotate-tokens is a no-op on first-time setup (no existing tokens to rotate).[/dim])existing discoveredrwzE [yellow]No known provider API keys found in env/Bitwarden.[/yellow]z, Set at least one of these and rerun setup:z - uU [yellow]⚠[/yellow] Detected provider env vars that the proxy does not yet cover:z [dim]These providers use request signing or SDK-minted OAuth (SigV4, service-account files) and will hold real credentials inside the sandbox. Egress isolation is INCOMPLETE for these.[/dim]z Provider envzUpstream hosts show_tokens)rkfrom_bitwarden_bitwarden_env_names_load_env_file_into_environrQr1discover_provider_mappings load_mappingsrOgetattrsysstdinisatty_prompt_proxy_state_direxistsrnowstrftimeshutilcopy2strOSErrormerge_mappingssorted_BEARER_PROVIDERSdiscover_uncovered_providers_mappings_table)rSrHruloadedr{rzrw state_dir mappings_srctsbackuprUrbenv_name uncoveredr?s&& rr^r^s '1=>%' 27;  & ' -.  MMN6(2pq r..CVC^C^Z^_J!H '$7 8F v( 99     MMv 34@ ;< c++-I$6L""$$\\^,,_="'=bT%BB S.F < xv>?  m   (RXYH  ]^ DEr334H MMF8*- .5//DWD_D_[_`I  mnD MMF4&/ *  _  MM/(N? MM3M?CD .~.>?@ A  Ii . ,d3 mm$78O )4 %& ~u - -). %& k ) MM^ _ K '  L */ %& o1o 7  se95667s$0J/ J/9J44 K!?KK!c(V^8dQhRRRRRRRR/#) rrSrrHrIrcr.rrr)rs"rrr%s+( ( 7( 2D( QU( Z^( rc  \P!4PRJpV'd\P!4\ VRR4pVRJgVRJdTpM?V'd6\ P P4'd\R4R9MRpMRpV'd\P!\VPRR44R7pVP'dRMR pV'dR MR pVPR V R VP RVP RV R2 4R#V'dVPR4R#R# \d2p TPRT R24TPR4Rp ? R#Rp ? ii;i)u[Stop a running daemon and decide whether to (re)start it with the new config. --restart → always (re)start; --no-restart → never (print the manual hint); neither + tty → ask only when a daemon was running; neither + !tty → restart iff one was running (first-time setup never auto-starts — matches the "configured, now run start" flow). Nr#TFz; Restart the running proxy now with the new config? [Y/n] rrg listeningznot yet listening restartedstartedriz% iron-proxy with the new config (pid=z, port=, r u> [yellow]⚠ could not start iron-proxy with the new config: ryzV Run [cyan]hermes egress start[/cyan] manually before launching new Docker sandboxes.u [yellow]⚠ stopped the running iron-proxy; config or tokens changed. Run [cyan]hermes egress restart[/cyan] (or [cyan]start[/cyan]) before launching new Docker sandboxes.[/yellow])yyes)r1 get_statuspid stop_proxyrrrrr start_proxyrOrrrQrrP) rSrHrc was_running restart_pref do_restart new_statusrverbrUs &&& rr`r`%s`--/%%T1K 4D1Lt|u4! yy!! Q R    4 n^b@c;deJ (2';';'; ATI"-;9D MM'v."'wz/E/E.Fb STV    R   t MMZ[^Z__hi j MMr s s ts#0E F&E==Fc V^8dQhRRRR/#rGr)rs"rrrPsE E &E 3E rc^\4p\4pVPR4;'g/pVPR4'gVPR4^#VPRR4pVPR4;'g/PR4pVR8H;'d'VRJ;'d\ VPR44pVR8XdIV'gA\ VPRR 44'dVPR 4M \ VR R 4#V'd.Ve*\ V4p\ VPRR 44VR&V'dT;'g/PR R4p\PPVR4P4'g\ VRV R2R4#T;'g/PR4'g\ VRR4#\P!\ VPRR44VVR7pTP'gTPR4^#TP'dRMRp TPRTP RTP RT 24^# \d p TPRT 24Rp ? ^#Rp ? ii;i) rruL[yellow]proxy.enabled is false — run `hermes egress setup` first.[/yellow]rrsecretsrNallow_env_fallbackFu[yellow]⚠ credential_source=bitwarden but secrets.bitwarden is disabled or missing — falling back to host-env secrets (allow_env_fallback=true). Rotated Bitwarden keys will NOT propagate.[/yellow]zTproxy.credential_source is 'bitwarden' but secrets.bitwarden is disabled or missing.zRe-enable it (`secrets.bitwarden.enabled: true`), switch back to env credentials with `hermes egress setup --no-bitwarden`, or set `proxy.allow_env_fallback: true` to opt into the host-env fallback.access_token_envBWS_ACCESS_TOKENrz credential_source=bitwarden but z is not set in the environment.ztEither export the access token, or run `hermes egress setup --no-bitwarden` to switch back to env-based credentials. project_idzFcredential_source=bitwarden but secrets.bitwarden.project_id is empty.zwRun `hermes secrets bitwarden setup` to configure the project, or switch back via `hermes egress setup --no-bitwarden`.rT)rhrefresh_secrets_from_bitwardenbitwarden_configu+[red]✗ failed to start iron-proxy:[/red] u1[red]✗ iron-proxy did not come up cleanly[/red]z[green]listening[/green]z"[yellow]not yet listening[/yellow]u+[green]✓[/green] iron-proxy running pid=z port=rM)rr rrQrO_refuser.osenvironstripr1rrPrrr) rHrSrrcrbw_cfg refresh_bw bw_access_envr(rUrs & rr3r3PsviG -C &&BI == # # de" &95Aggi &&B + +K 8F#{2iivT7IiidSYS]S]^gShNiJK'  2E: ; ; MMv  fn f(f'+IMM:NPU,V'W#$2**+=?QR zz~~mR066882=/A`a`   "!!,//XT  #IMM.$$GH+5#  ::: IJ/5/?/?/?+EiI MM 5fjj\I[I[H\\^_h^ij   CC5IJs%2J J, J''J,c V^8dQhRRRR/#rGr)rs"rrrs  % # rc\4p\P!4'dVPR4^#VPR4^#)u%[green]✓[/green] iron-proxy stoppedz%[dim]iron-proxy was not running[/dim])rr1rrQrHrSs& rr4r4s8iG }} =>   => rc V^8dQhRRRR/#rGr)rs"rrrs(Src\4p\P!4'dVPR4\ V4#)z^Stop the daemon (if any) then delegate to ``cmd_start`` so every credential-source guard runs.z)[dim]stopped the running iron-proxy[/dim])rr1rrQr3rs& rr5r5s+iG }} AB T?rc V^8dQhRRRR/#rGr)rs"rrrs  ' C rc\4p\P!4TP R4TP R4^# \d pTP RT 24Rp?^#Rp?ii;i)aHot-reload the ruleset via the management API (no restart, no dropped connections). New upstream SECRETS still need ``hermes egress restart``: the daemon reads credentials from its own environment at spawn time and a reload does not re-populate that env. u[red]✗ reload failed:[/red] Nu[[green]✓[/green] iron-proxy ruleset reloaded in-place (no restart, connections preserved)u[dim]Note: new upstream secrets (rotated keys, new providers) still need `hermes egress restart` — the daemon reads real credentials from its environment at spawn time.[/dim])rr1 reload_proxyrPrQ)rHrSrUs& rr6r6si iG  MMop MM @   6se<=sA A/A**A/r}Fc V^8dQhRRRR/#)rr}rOrrr)rs"rrrstrc "\4pVPR4;'g/p\P!4pRR.pVP R\ W#RRR744VP R4\P!4pV'dVP RR .4VFjpV'd VPM\VP4pVP R VP R V R R PVP4 R24Kl \P!4pV'd1VP RR.4VFp VP R V 24K \VPR44'd'VP'gVP RR.4MW\VPR44'd8VP 'dVP"'gVP RR.4RPV4#)zDPlain-text egress status for slash commands, Dashboard, and Desktop.rzEgress proxy statusrc34"TFwrV RV 2xK R#5i): Nr).0labelvalues& r %format_status_text..s$oLE 'E7oscV'dR#R#)rnor)vs&r$format_status_text..sRSI]Y]I]rcV#)Nrts&rrrsmnryndimz*Scope: Docker backend only in this releasezToken mappings: - rz (rr zHUncovered providers (real credentials still visible inside the sandbox):rzDNext: run `hermes egress setup` to mint tokens and write proxy.yaml.zBNext: run `hermes egress start` before launching Docker sandboxes. )r rr1rextend _status_rowsappendr proxy_tokenr real_env_namejoinupstream_hostsrrO configuredrr) r}rrcr(linesrbmtokrr?s $ rformat_status_textr s -C &&BI ]]_F "B 'E LL(?]cno LL=>!H b+,-A#.!--K 4NC LL403%r$))ADTDT:U9VVWX Y//1I bdefD LL4v ' IMM) $%%f.?.?.? b`ab immI& ' '@P@P@P b^_` 99U rc V^8dQhRRRR/#rGr)rs"rrrs  ' C rc 6\4p\4pVPR4;'g/p\P!4p\ RRRR7pVP RRR7VP R4\W4\RR7FwrgVPWg4K VPV4\P!4pV'dmVP4VPR 4VP\VR R VPR 74VP'dVPR 4\P!4p V 'd?VP4VPR4V Fp VPRV 24K ^#)rFN) show_headerboxpaddingrboldstylecRV R2#)z[dim]rxrrs&rrcmd_status..sPUVWUXX^N_rrzold]Token mappings[/bold]zReal envUpstreamr|u[yellow]⚠[/yellow] proxy tokens just printed in full — they may persist in your shell history. Consider clearing it after this command.zY[yellow]Uncovered providers[/yellow] (real credentials still visible inside the sandbox):r)r)rr rr1rr add_columnr_ynadd_rowrQrrr}r) rHrSrrcr(tablerrrbrr?s & rr7r7s:iG -C &&BI ]]_F ev >E Rv& R$Y3D_`  e#a MM%!H  34 oh JTXTdTdef     MMd  //1I  qrD MMD- ( rc V^8dQhRRRR/#rGr)rs"rrrs  ( S rcL\4p\4pVPR/4pVPR4'gVP R4^#RVR&\ V4VP R4\ P!4PeVP R4^#)rrz+[dim]proxy.enabled was already false.[/dim]Fu-[green]✓[/green] proxy.enabled set to falseug iron-proxy is still running — stop it with [cyan]hermes egress stop[/cyan] if you want it down too.) rr rrrQr r1rr)rHrSrrcs& rr8r8siG -Cw+I == # # CD Ii MMAB }}& u  rc V^8dQhRRRR/#rGr)rs"rrr s  ' C rc\4p\P!4pVPfVP R4^#VP \ VP44^#)NuD[yellow](no config generated — run `hermes egress setup`)[/yellow])rr1r config_pathrQr)rHrSr(s& rr9r9 sJiG ]]_F ! \] MM#f(()* rc V^8dQhRRRR/#)rrSrrzOptional[list[str]]r)rs"rrrs##'#.A#rc2\4pVPR4;'g/PR4;'g/pVPR4'g%VPR4VPR4R#^RIHpVPRR 4p\ P PVR 4P4pV'gVPR V R 24R#VPWRPR R 4^RR7wrg\VP44pV'gVPR4R#VPR\V4 R24V# \d2p TPRT R24TPR4Rp ? R#Rp ? ii;i)zSecret names from Bitwarden for ``setup --from-bitwarden``; prints the error and returns ``None`` on any failure so the wizard aborts loudly instead of falling back to the host env. rrruS [red]✗ --from-bitwarden requested but secrets.bitwarden.enabled is false.[/red]zG Run `hermes secrets bitwarden setup` first, or omit --from-bitwarden.N)rrrru* [red]✗ --from-bitwarden requested but z% is not set in the environment.[/red]rF) access_tokenrcache_ttl_seconds use_cacheu [red]✗ Bitwarden returned an empty secrets list.[/red] Check the project_id in secrets.bitwarden and the BWS access-token's project scope.z Pulled z env names from Bitwarden.u2 [red]✗ Could not enumerate Bitwarden secrets: rjz Either fix the Bitwarden config and retry, or rerun setup without --from-bitwarden (the proxy will read secrets from the host process env at start time).) r rrQagent.secret_sourcesrrrrfetch_bitwarden_secretsrkeyslenrP) rSrrbw token_envr#r_namesrUs & rrrsg -Cggi &&B + +K 8 > >BF ::i  kl _`8JJ13EF zz~~i4::<  MMFykQvw x//%**\22Nbcot0 W\\^$ MMh  #e*-GHI  J3%vVW  n  s,;A E E AE:E F%&FFcV^8dQhRR/#)rrr0r)rs"rrr=sSrc\4p^p\\P4\\P 4,pTFpT\ P9d.\ PT,P4'dKETPT4;'gRP4pT'gKxT\ PT&T^, pK T# \d^#i;i)zBackfill known provider keys from ``~/.hermes/.env`` into ``os.environ``; returns the count. Never overrides an exported value; only known provider names, so unrelated secrets stay out.r) r rPsetr1r_NON_BEARER_PROVIDERSrrrr)file_envaddedknownr?vals rrr=s: E $$ %B,D,D(E EE 2:: "**T"2"8"8":": ||D!''R..0 3"BJJt  QJE  L s C!! C0/C0c(V^8dQhRRRRRRRR/#)r env_headerr hosts_headerr}rOrrr)rs"rrrPs*#SRV[`rcb\RRR7pVPVRR7VPVRR7VPRRR7VFbpV'd VPM\VP4pVP VP RP VP4V4Kd V#) Tr)r header_stylerYrrz Proxy tokengreenr)rrrr rrrr)rbr7r8r}rr r s&&&$ rrrPs d 8E Zv. \/ ]'2 *amm AMM0J aootyy1A1A'BCH Lrc(V^8dQhRRRRRRRR/#) rrSrnr0titlerrrr)rs"rrr[s(5575s53545rcTVP4VPRV RV 24R#)z [bold]Step z [/bold] NrQ)rSr=r>s&&&rrkrk[s$ MMO MMKs)E734rc(V^8dQhRRRRRRRR/#)rrSrreasonrhintrr0r)rs"rrr`s(  W c   rcXVPRV R24VPRV 24^#)uXPrint a ``✗ Refusing to start`` headline plus an indented remedy; returns exit code 1.u[red]✗ Refusing to start: rjrMr@)rSrBrCs&&&rrr`s- MM0?@ MMBtf+ rc V^8dQhRRRR/#)rrrOrrr)rs"rrrgs>>t>>rcV'dR#R#)z[green]yes[/green]z [dim]no[/dim]r)rs&rrrgs#( =o=rc V^8dQhRRRR/#)rtextrrr)rs"rrrks##rcv\V4P4P4# \dR#i;i)zJ``input()`` lowered+stripped; EOF (closed stdin) reads as an empty answer.r)inputrlowerEOFError)rHs&rrrks5T{  "((** s &) 88c V^8dQhRRRR/#)rrcr.rzlist[tuple[str, str]]r)rs"rrrssD9NrcRV!\VPR4443R\VP;'g V!R443RVP;'g V!R43R\VP ;'g V!R443R \VP ;'g V!R443R \VP43R VP'dR VP 2MV!R 43RV!VP43R\VPRR443RV!\VPRR4443. #)z``(label, value)`` rows shared by the rich ``status`` table and the plain-text variant; ``yn`` renders booleans, ``dim`` wraps placeholder text for missing values.EnabledrBinaryz (missing)zBinary versionz (unknown)Configz(not generated)zCA certz Tunnel portProcesszpid z (stopped) ListeningzCredential srcrrzDocker enforcerT) rOrr binary_pathbinary_versionr  ca_cert_pathrrr)rcr(rrs&&$$rrrss% BtIMM)4567 3v))==S-=>? 600DDC 4DE 3v))CCS1B-CDE C++EEs3D/EFG F../0 6:::d6::,'3{;KL b))*+ 3y}}-@%HIJ 2d9==1Dd#KLMN  r)2__doc__ __future__rargparserrrrtypingrr rich.consoler rich.panelr rich.tableragent.proxy_sourcesr r1 agent.redactr hermes_cli.configr r r rEr-r/r\r]r^r_r`r3r4r5r6r r7r8r9rrrrkrrrrrrrras-" ! 0$@@1'h  ! H BJIX( VE P  *e: > & #L&5  >r