Dext is pre-1.0. Security fixes are handled on main unless release branches are introduced later.

Do not open a public issue for secrets, credential leakage, prompt/session disclosure, sandbox escape, or provider-auth flaws.

Report privately to the repository owner through GitHub private vulnerability reporting if enabled, or contact the owner directly.

Please include:

• Affected commit/version.
• Operating system and shell.
• Minimal reproduction steps.
• Whether credentials/session exports/logs are involved.
• Any relevant redacted logs.

Never commit real credentials. The following must remain local/private:

• .env
• .dext/
• .dext/checkpoints/ recovery manifests and sidecars
• ~/.dext/auth.json
• ~/.dext/providers.json if it contains private endpoints or tokens
• dext-session-*.jsonl
• dext-session-*.html
• DEXT.todo.json
• terminal/session logs and crash snapshots

Use .env.example for documented variable names only. Do not put real values there.

Dext sessions and exports can contain:

• User prompts.
• Model responses.
• Tool inputs/outputs.
• Local paths and filenames.
• Environment snippets.
• Accidentally pasted credentials.

Review and redact before sharing.

Before pushing public code:

git status --short --ignored
git grep -n -I -i -E 'api[_-]?key|secret|token|oauth|authorization|bearer|password|private[_-]?key|refresh[_-]?token|client[_-]?secret'
find . -path ./.git -prune -o -path ./target -prune -o -type f -print
cargo build --release
cargo test --release
cargo test --release --test tui_smoke -- --nocapture

Also scan untracked and ignored files before deciding what to preserve locally vs. delete.

• --approval ask is the conservative default for privileged tools.
• --approval never prevents privileged tool execution.
• --sandbox-profile read-only (or --sandbox read-only) is recommended for review-only tasks.
• --trust and danger-full-access are high-trust modes. Use only in controlled environments.
• Dext Git checkpoints are best-effort local recovery aids. They may include file content in hidden refs or .dext/checkpoints/ sidecars, and they do not cover arbitrary external side effects.
• OAuth/API-key login should use Dext's official CLI/slash flows. Do not copy credentials from unrelated tools or stores.