* feat(cli): expose identifiers for saved scan follow-up
* test(sdk): exercise dedupe representatives in publication
* feat(cli): make project setup and authentication easier to inspect
* docs(cli): distinguish sign-in flows and credential sources
* feat(cli): link interrupted scans and imported evidence to their next commands
* fix(cli): make command help and discovery reflect runnable workflows
* build(sdk): include the command argument helper in package checks
* refactor(cli): reuse shell path quoting for project previews
* docs(cli): identify the shell used for Windows preview commands
* test(cli): account for the internal publication CSV in help coverage
* fix(cli): scope recovery hints to supported sessions and shells
* fix(cli): declare exclusive scan import sources in the schema
* refactor(cli): share credential locking and project preview preparation
* fix(cli): resolve repository arguments consistently during scan discovery
* refactor(cli): simplify the result handoffs and verify PowerShell recovery
* fix(cli): check sign-in from the same directory in every format
* fix(cli): preserve diagnostics when project initialization fails
---------
Co-authored-by: Codex <noreply@openai.com>
* feat(cli): expose identifiers for saved scan follow-up
* test(sdk): exercise dedupe representatives in publication
* feat(cli): link interrupted scans and imported evidence to their next commands
* fix(cli): make command help and discovery reflect runnable workflows
* build(sdk): include the command argument helper in package checks
* test(cli): account for the internal publication CSV in help coverage
* fix(cli): scope recovery hints to supported sessions and shells
* fix(cli): declare exclusive scan import sources in the schema
* fix(cli): resolve repository arguments consistently during scan discovery
* refactor(cli): simplify the result handoffs and verify PowerShell recovery
---------
Co-authored-by: Codex <noreply@openai.com>
* fix(cli): inspect integration commands before installation
* fix(cli): include the integration dispatcher in package validation
* fix(cli): list generated skills at the requested grouping depth
* docs(cli): clarify which installation skills list checks
* refactor(cli): share integration commands across dispatch and discovery
* fix(cli): complete integration flags without executing their commands
* fix(cli): register MCP clients through the installed SDK dependency
* fix(cli): preserve shell completion words and cursor positions
* fix(cli): serve all shell completions before executable dispatch
---------
Co-authored-by: Codex <noreply@openai.com>
* fix(cli): update the active installation and migrate legacy options
* fix(cli): recognize local projects named lib during updates
* fix(cli): use supported pnpm workspace and Bun optional flags
* fix(cli): isolate self-updates from project configuration
* fix(cli): recognize global npm under nvm checkouts
* refactor(cli): simplify package manager update resolution
* refactor(cli): skip updater registration during inspection
* refactor(cli): share metadata flags with update notices
---------
Co-authored-by: Codex <noreply@openai.com>
* feat(cli): expose identifiers for saved scan follow-up
* test(sdk): exercise dedupe representatives in publication
* feat(cli): link interrupted scans and imported evidence to their next commands
* build(sdk): include the command argument helper in package checks
* fix(cli): scope recovery hints to supported sessions and shells
* refactor(cli): simplify the result handoffs and verify PowerShell recovery
* fix(scan): reduce setup and tool output in Standard scans
* fix(workbench): keep policy paths optional for scan lookups
* fix(sdk): retain the preflight callback before scan dispatch
* fix(workbench): only advertise scoped inventory for Standard scans
* docs(workbench): explain optional scope report failures
* fix(workbench): preserve the Deep Scan registration response
* test(workbench): use the current scan context request in the Deep Scan fixture
---------
Co-authored-by: mldangelo-oai <269034524+mldangelo-oai@users.noreply.github.com>
* docs: add a local import guide for Semgrep hosted MCP findings
* docs: extend the hosted Semgrep import example through Cloud
* docs: clarify the Semgrep Cloud workspace prerequisite
---------
Co-authored-by: Michael D'Angelo <269034524+mldangelo-oai@users.noreply.github.com>
* fix(plugin): scope legacy scan continuations to the attached scan
* fix(plugin): rejoin attached legacy deep scans by target
* fix(plugin): keep attached deep scan results with their conversation
* fix(scan): isolate Git display settings in content snapshots
* fix(scan): pin hunk, file order, and rename rendering in snapshots
* test(scan): write Git order fixtures with LF on every platform
* fix(scan): stabilize submodule, indentation, and rename presentation
* Capture the configured submodule diff before asserting
* Normalize Git driver annotations and binary patch rendering
* Stage validated custom ZIP plugins for Windows scans
* Support long Windows plugin ZIP staging paths
* Prefer shorter trusted paths for Windows ZIP scan plugins
* Keep Windows path-length and ZIP publication tests independently mergeable
* Cancel slow Windows scan-input parent lookup promptly
* Verify ZIP fixtures exercise their temporary-path spies
* test: accept either eligible Windows ZIP resume stage parent
* test(windows): allow the CI timeout for ZIP workspace reuse
* test: restore owned sticky parents before cleanup
---------
Co-authored-by: mldangelo-oai <269034524+mldangelo-oai@users.noreply.github.com>
Co-authored-by: Codex <codex@users.noreply.github.com>
* fix(windows): preserve long Git metadata in reviewed patch replay
* fix(windows): keep reviewed patch replay within source limits
* fix(windows): preserve metadata-free LF patch replay
* test(workbench): select short replay case only on Windows
---------
Co-authored-by: Codex <codex@users.noreply.github.com>
* fix(scan): verify assumed-unchanged files for committed diffs
* test(workbench): read the index flag before asserting
* fix(workbench): isolate Git settings during private index refresh
* fix(workbench): preserve explicit usage database paths
* test(workbench): close usage fixtures before renaming them
* test(workbench): use supported database names on each host
* fix(runtime): honor literal POSIX executable override paths
* fix(runtime): retain the lookup origin of padded executable paths
* fix(runtime): keep bare executable overrides on their original lookup path
* fix(windows): resume Deep Scans before the first checkpoint
* fix(windows): retain the resume directory handle through registration
* fix(windows): finish Deep output registration after cancellation
* fix(windows): retain registration control across plugin entrypoints
* fix(windows): read Deep resume identities from pinned handles
* fix(windows): preserve Deep Scan checkout identity across Python versions
* fix(windows): verify bound checkouts throughout Deep Scan recovery
* fix(workbench): keep scan history when a legacy checkout moves
* test: include checkout binding in migration expectations
---------
Co-authored-by: mldangelo-oai <269034524+mldangelo-oai@users.noreply.github.com>
Co-authored-by: Codex <codex@users.noreply.github.com>
* fix(plugin): publish new patch files on musl without hard links
* test(plugin): close the rename fixture directory explicitly
* test(plugin): select the raw rename syscall test only on Linux
---------
Co-authored-by: mldangelo-oai <269034524+mldangelo-oai@users.noreply.github.com>
Deep Scan accepts --stop-after-no-new 1 and --max-discovery-runs 1, but
the completion summary then said "The last 1 review rounds" or "Reached
the limit of 1 review rounds". Use the singular when the count is one.
Co-authored-by: mldangelo-oai <269034524+mldangelo-oai@users.noreply.github.com>
* fix(plugin): fall back to system Python when a Linux UID has no home
* fix(sdk): discover system Python when a Linux UID has no home
---------
Co-authored-by: mldangelo-oai <269034524+mldangelo-oai@users.noreply.github.com>
* fix(publish): explain when Cloud import is unavailable
`publish findings --to cloud` starts with the repository catalog. For a
ChatGPT account or deployment without Codex Security Cloud import, that
request returns 404 and the CLI printed only "Cloud import failed (HTTP
404). Not found", which does not say whether the repository, the file, or
the account was missing.
Keep the server's text and add the same explanation `publish scan` gives
for this case: Cloud import is not available for this account or
deployment. Other statuses and endpoints are unchanged.
* fix(publish): handle an empty catalog error response
* docs(imports): correct AWS Continuum and mktemp guidance
- Name the first AWS CLI v2 release with `aws continuum` (2.38.5); earlier
v2 releases reject the command.
- Say that validation results come with findings Continuum detects, while
findings submitted to Continuum can omit them.
- macOS `mktemp -d` ignores TMPDIR, so the advice to set TMPDIR did not
move report directories there. Suggest a template instead.
* docs(imports): honor temporary report paths and clarify validation evidence
* fix(imports): read Continuum weakness IDs from subCategory
Findings that AWS Continuum detects itself omit cweIds and name their
weakness only in subCategory, for example "CWE-89: Improper
Neutralization ...". The reader mapped weakness_ids from cweIds alone,
so every native Continuum code finding imported without a CWE.
Fall back to the leading CWE ID in subCategory when cweIds is absent.
Explicit cweIds still win, and the previous-release replay projection
keeps reading cweIds only.
* fix(imports): preserve Continuum replay and evidence admission
* fix(cli): point native sign-in hints at codex-security login
After starting browser sign-in, native Codex prints "On a remote or
headless machine? Use `codex login --device-auth` instead." Running that
command signs in to the regular Codex home, not the Codex Security
credential home, so the suggested recovery does not help.
For the sign-in commands that pass native output straight through
(login, login status and logout), forward native stderr through a small
streaming rewrite of `codex login` to `codex-security login`. Stdin and
stdout stay attached to the terminal, other output is unchanged, and only
a possible partial match is held back between chunks.
* fix(cli): forward login hints and reap interrupted sign-ins
* fix(auth): sign in with the credential storage set in Codex config
On macOS, a fresh `codex-security login` could not be used to publish to
Cloud. Scans write `cli_auth_credentials_store = "auto"` into the Codex
Security credential home, so native login saved the token in the system
keyring and removed auth.json, while Cloud publication reads file-backed
credentials only.
The documented fix, setting `cli_auth_credentials_store = "file"` in
Codex config.toml and signing in again, had no effect: `login` used
whatever the last scan wrote, and SDK scans ignored the user's Codex
config for sign-in settings (only skill commands mirrored it).
- Layer the user's Codex config sign-in settings
(cli_auth_credentials_store, forced_login_method,
forced_chatgpt_workspace_id) between the wrapper defaults and explicit
overrides in mergedCodexConfig, so scans, their runtime config and Deep
Scan workers use them. A Codex config that cannot be read or parsed
sets no preference here; the commands that use it still report why.
- Before `login` and `login status`, write the keys that config sets into
the credential home. Native argv is unchanged, so managed policy still
wins. Unset keys and `logout` leave the stored location alone.
- Make the Cloud sign-in error and CLI docs name the setting and command.
* fix(cli): exit interrupted login when stderr stops draining
* fix(auth): keep sign-in, credential cleanup, and Cloud publication consistent
* fix(sdk): cancel queued logins without aborting settled operations
* test(sdk): guard the budget cancellation wait after usage is recorded
---------
Co-authored-by: mldangelo <michael.l.dangelo@gmail.com>