[PR #240] [MERGED] feat(cli): enable secure sandboxes by default #281

New issue

Closed

opened 2026-10-29 14:21:47 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-29 14:21:47 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/kvcache-ai/AgentENV/pull/240
Author: @yingdi-shan
Created: 9/2/2026
Status: ✅ Merged
Merged: 9/3/2026
Merged by: @LSX-s-Software

Base: main ← Head: feat/aenv-secure-by-default

📝 Commits (1)

d35b311 feat(cli): enable secure sandboxes by default

📊 Changes

6 files changed (+35 additions, -24 deletions)

View changed files

📝 crates/aenv/src/client/sandboxes.rs (+6 -10)
📝 crates/aenv/src/commands/start.rs (+15 -6)
📝 docs/src/concepts/authentication.md (+3 -2)
📝 docs/src/concepts/sandboxes.md (+5 -3)
📝 docs/src/concepts/snapshots.md (+3 -1)
📝 docs/src/getting-started/aenv-cli.md (+3 -2)

📄 Description

Summary

make warm and cold aenv start requests always enable secure sandbox authentication
remove the redundant --secure option and reject it during argument parsing
update CLI and concept documentation to describe automatic envd access-token management

Compatibility

Existing scripts that pass aenv start --secure must remove the flag. The AgentENV HTTP API remains unchanged and continues to support explicit secure-mode selection for non-CLI clients.

Testing

cargo fmt --package aenv -- --check
cargo test -p aenv
cargo clippy -p aenv --all-targets -- -D warnings
inspected aenv start --help to confirm --secure is absent

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/kvcache-ai/AgentENV/pull/240 **Author:** [@yingdi-shan](https://github.com/yingdi-shan) **Created:** 9/2/2026 **Status:** ✅ Merged **Merged:** 9/3/2026 **Merged by:** [@LSX-s-Software](https://github.com/LSX-s-Software) **Base:** `main` ← **Head:** `feat/aenv-secure-by-default` --- ### 📝 Commits (1) - [`d35b311`](https://github.com/kvcache-ai/AgentENV/commit/d35b311b27cc21b67ae7afe6b3bdf26664f5f224) feat(cli): enable secure sandboxes by default ### 📊 Changes **6 files changed** (+35 additions, -24 deletions) <details> <summary>View changed files</summary> 📝 `crates/aenv/src/client/sandboxes.rs` (+6 -10) 📝 `crates/aenv/src/commands/start.rs` (+15 -6) 📝 `docs/src/concepts/authentication.md` (+3 -2) 📝 `docs/src/concepts/sandboxes.md` (+5 -3) 📝 `docs/src/concepts/snapshots.md` (+3 -1) 📝 `docs/src/getting-started/aenv-cli.md` (+3 -2) </details> ### 📄 Description ## Summary - make warm and cold `aenv start` requests always enable secure sandbox authentication - remove the redundant `--secure` option and reject it during argument parsing - update CLI and concept documentation to describe automatic envd access-token management ## Compatibility Existing scripts that pass `aenv start --secure` must remove the flag. The AgentENV HTTP API remains unchanged and continues to support explicit secure-mode selection for non-CLI clients. ## Testing - `cargo fmt --package aenv -- --check` - `cargo test -p aenv` - `cargo clippy -p aenv --all-targets -- -D warnings` - inspected `aenv start --help` to confirm `--secure` is absent --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-29 14:21:47 +00:00