Skip to content

OpenAI's Codex Security CLI and TypeScript SDK for finding, validating, and fixing security vulnerabilities. npm: https://www.npmjs.com/package/@openai/codex-security

fix(plugin): honor signed-in tracker connections for finding reads (#2212)

Michael D'Angelod5177fa4f7ac
diff --git a/docs/plugin-connectors.md b/docs/plugin-connectors.md
index ac332855a..2ed1b6429 100644
--- a/docs/plugin-connectors.md
+++ b/docs/plugin-connectors.md
@@ -28,7 +28,7 @@ explicit choice of account or transport.
Connect the **Atlassian** app in the app directory. Existing Atlassian Rovo (Legacy) connections do not connect the new app; authorize it separately with the intended account and site.
-Intake and duplicate checks need read and search access. Creating or updating issues also needs write access. Before creating an issue, the tracking skill resolves the project, issue type, and required fields.
+For user-selected Jira CLI or Linear MCP reads, see the [ticket intake guide](../plugins/codex-security/skills/triage-finding/references/ticket-intake.md#retrieval). Intake and duplicate checks need read and search access. Creating or updating issues also needs write access. Before creating an issue, the tracking skill resolves the project, issue type, and required fields.
Use the app's live schemas and discover deferred operations when needed. See Atlassian's [supported tools](https://developer.atlassian.com/cloud/rovo-mcp/guides/supported-tools/) and the skill's [Jira workflow](../plugins/codex-security/skills/track-findings/references/jira.md).
@@ -36,7 +36,7 @@ Use the app's live schemas and discover deferred operations when needed. See Atl
Test the plugin build with synthetic findings in a selected QA project:
-- Verify that Jira calls use the new Atlassian app and the selected account and site.
+- Verify that Jira tracking uses the Atlassian app and that intake reads use the selected connection and account on the intended site or workspace.
- Read a synthetic issue directly and through project-scoped JQL, including pagination.
- Create one issue, reuse it without creating a duplicate, and update approved fields. Verify each write by reading the issue back.
- Verify that missing connections and insufficient access produce recovery guidance without duplicate creates.
diff --git a/evals/triage-finding/scripts/test-app-surface-instructions.mts b/evals/triage-finding/scripts/test-app-surface-instructions.mts
index f8a857e23..222e52891 100644
--- a/evals/triage-finding/scripts/test-app-surface-instructions.mts
+++ b/evals/triage-finding/scripts/test-app-surface-instructions.mts
@@ -22,6 +22,8 @@ assert.match(
);
assert.match(ticketIntake, /natural-language search[\s\S]*discover[\s\S]*JQL/);
assert.match(ticketIntake, /exhaust[\s\S]*pag(?:es|ination)/i);
+assert.match(ticketIntake, /workitem search .*--fields "\$fields" --paginate/);
+assert.match(ticketIntake, /workitem view .*--fields "\$fields"/);
assert.match(ticketIntake, /missing connector|connector.*unavailable/i);
assert.match(ticketIntake, /authentication|reauthorize/i);
assert.match(ticketIntake, /insufficient permission|request access/i);
diff --git a/evals/triage-finding/tests/ticket-intake.yaml b/evals/triage-finding/tests/ticket-intake.yaml
index 7c8f44446..2df989fd4 100644
--- a/evals/triage-finding/tests/ticket-intake.yaml
+++ b/evals/triage-finding/tests/ticket-intake.yaml
@@ -6,7 +6,7 @@
case_id: ticket-connector-unavailable
target_repo: evals/triage-finding/fixtures/repo
source_type_under_test: scanner_ticket
- finding_input: "Linear issue SEC-293. Connector observation: the Linear connector is unavailable because it is not connected."
+ finding_input: "Linear issue SEC-293. Connector observation: the Linear app is not connected and no other authenticated connection can read this Linear workspace."
invocation_preamble: "Use $codex-security:triage-finding to import Linear issue SEC-293."
expected_ticket_failure: unavailable
eval_instructions: &failedReadInstructions |-
diff --git a/plugins/codex-security/skills/track-findings/SKILL.md b/plugins/codex-security/skills/track-findings/SKILL.md
index 5e45ac93f..ffa2f8b8c 100644
--- a/plugins/codex-security/skills/track-findings/SKILL.md
+++ b/plugins/codex-security/skills/track-findings/SKILL.md
@@ -34,7 +34,9 @@ Honor the user's current choice, then current repository or organization policy.
- GitHub issues: resolve the exact repository from the user's choice or the sealed target and verify it live. Accept HTTPS or SSH remotes that resolve unambiguously to that repository. Sensitive findings default to a private repository. Internal or public visibility requires a warning and explicit confirmation.
- GitHub advisories: use the verified public canonical non-fork source repository for a sealed `git_revision`, with the access required by the advisory reference. Do not use an external tracker or fall back to an issue.
-For CLI runs, check `gh --version`, `gh auth status --hostname <host>`, and `gh repo view https://<host>/<owner>/<repo>`. Confirm repository identity, live visibility, viewer permission, and issue availability for issue runs. Missing required metadata, authentication warnings, insufficient permission, or an ambiguous repository block the run.
+Before any source or destination request with `gh`, use a context that keeps the selected identity fixed on that host throughout the operation. Verify the effective login with `gh auth status --active --hostname <host>` when `gh auth status --help` lists `--active`. Otherwise inspect the active or sole account in `gh auth status --hostname <host>`. An environment token can override a saved account. If the context cannot stay fixed, the login differs, or the selected account reports authentication errors or warnings, skip optional source links as described below. Stop GitHub tracking if its destination connection fails this check. Ignore failures confined to explicitly inactive accounts.
+
+For GitHub destinations, check the repository through the selected GitHub app or, for CLI runs, with `gh repo view https://<host>/<owner>/<repo>`. Confirm repository identity, live visibility, viewer permission, and issue availability for issue runs. Missing required repository metadata, insufficient permission, or an ambiguous repository block tracking at that GitHub destination.
For GitHub, use one transport and identity through source checks, duplicate discovery, writes, and readback. Use a fully qualified `https://<host>/<owner>/<repo>` URL for CLI repository commands and pass `--hostname <host>` on every `gh api` call. Advisories use `github.com`. Shell-quote locators, queries, titles, metadata, and complete endpoints; validate owner and repository as separate segments and encode contents paths and refs as data. Never interpolate scan content into shell source or use `eval`.
diff --git a/plugins/codex-security/skills/triage-finding/references/ticket-intake.md b/plugins/codex-security/skills/triage-finding/references/ticket-intake.md
index 8b6aee259..8383241c7 100644
--- a/plugins/codex-security/skills/triage-finding/references/ticket-intake.md
+++ b/plugins/codex-security/skills/triage-finding/references/ticket-intake.md
@@ -4,13 +4,15 @@ Retrieve the requested content before normalization. Do not infer inaccessible t
## Retrieval
-Use the native [Atlassian](app://asdk_app_6a83901dde988191b3f3cefdcc19acfa) app for Jira. Resolve identity and site with `atlassianUserInfo` and `getAccessibleAtlassianResources`; keep that connection and site for the selected set. Ask when the source is ambiguous.
+By default, use the native [Atlassian](app://asdk_app_6a83901dde988191b3f3cefdcc19acfa) app for Jira. Resolve identity and site with `atlassianUserInfo` and `getAccessibleAtlassianResources`; keep that connection and site for the selected set. Ask when the source is ambiguous.
Use live schemas: `getJiraIssue` for exact issues and `searchJiraIssuesUsingJql` for collections. Exhaust returned pages. Discover deferred metadata through `discover` and `executeRead`; intake does not invoke write tools.
-Use natural-language search to discover a site, project, issue family, or first key from a vague request, then use JQL or exact fetches. Order collection queries by a stable field and preserve the JQL as provenance. Jira text search tokenizes punctuation: if an exact marker gives no results, search a stable token and filter returned summaries for the exact family.
+Use natural-language search to discover a site, project, issue family, or first key from a vague request, then use JQL or exact fetches. Keep user-supplied JQL intact. Order queries you build by a stable field and preserve the JQL as provenance. Jira text search tokenizes punctuation: if an exact marker gives no results, search a stable token and filter summaries for the exact family when those fields are authorized.
-For Linear, fetch exact URLs or identifiers directly. Search team, project, or phrase requests to resolve the intended issue set, then fetch every selected issue before normalization.
+Use a user-selected Atlassian CLI only in an already authenticated environment dedicated to the authorized Jira site and account throughout intake, including after a pause. `acli jira auth status` identifies its active login. If that scope cannot stay fixed, ask for a scoped export or connection. When JQL defines the complete authorized set, retrieve the requested fields directly with `acli jira workitem search --jql "$jql" --fields "$fields" --paginate --json`. For broader searches, request only permitted selection fields, such as `key,summary` for a title match, and filter candidates before fetching bodies. If those fields cannot establish membership, ask for exact keys. Parse all results locally. Use `acli jira workitem view "$key" --fields "$fields" --json` for exact keys or missing authorized details of selected issues. Verify returned keys and sites when available and page requested comments.
+
+For Linear, use the native app by default. If the user selects an authenticated [Linear MCP connection](https://linear.app/docs/mcp), verify the active account and workspace and use its read operations. Fetch exact URLs or identifiers directly. Search team, project, or phrase requests to resolve the intended issue set, then fetch every selected issue before normalization.
## Linear parents and sub-issues
@@ -24,7 +26,7 @@ Keep one result per selected issue in deterministic breadth-first tree order: pa
## Retrieval failures
-- Missing connector or authentication: state which source is unavailable and ask to connect or reauthorize it.
+- Missing connector or authentication: state which source is unavailable and offer reconnection or a configured read path for the user to select.
- Insufficient permission: report the access error and ask the user to request access or choose an account with access.
- Not found or inaccessible: ask to verify the identifier and workspace. Do not claim the issue does not exist when it may be hidden.
- Transient failure: retry when likely to help, keeping the same source and scope. Report unresolved errors.