Skip to content

fix(agent): redact error event messages - #96

Open
XnLemon wants to merge 1 commit into
mainfrom
codex/phase2-agent-error-event-redaction
Open

fix(agent): redact error event messages#96
XnLemon wants to merge 1 commit into
mainfrom
codex/phase2-agent-error-event-redaction

Conversation

@XnLemon

@XnLemon XnLemon commented Jul 11, 2026

Copy link
Copy Markdown
Owner

Objective

Redact model-visible agent error event messages for Phase2 redaction closure.

Completed Changes

  • Route n8n sendErrorEvent error messages through the shared platform redactor.
  • Route WeKnora sendErrorEvent error messages through the shared platform redactor.
  • Add regression coverage for Authorization, api_key, and Cookie leakage strings in both agents.

Validation

  • cd agent/n8n && go test ./...
  • cd agent/weknora && GOPROXY=https://goproxy.cn,direct go test ./...
  • cd agent/n8n && go vet ./...
  • cd agent/weknora && GOPROXY=https://goproxy.cn,direct go vet ./...
  • git diff --check
  • Subagent open-code-review: 0 High / 0 Medium / 0 Low

Known Risks / Limitations

  • The first WeKnora test attempt hit proxy.golang.org download timeouts; reran successfully with GOPROXY=https://goproxy.cn,direct.
  • This increment is scoped to n8n and WeKnora agent error events; A2A agent error event redaction remains a follow-up.

Follow-up Work

  • Continue Phase2 closure by auditing and redacting remaining model-visible agent error surfaces, starting with A2A.

@coderabbitai

coderabbitai Bot commented Jul 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@XnLemon, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 18 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a1f59768-9abf-4b42-8140-e073bc79d2c8

📥 Commits

Reviewing files that changed from the base of the PR and between 361e2a4 and 66f0ebf.

📒 Files selected for processing (4)
  • agent/n8n/n8n_agent.go
  • agent/n8n/n8n_agent_test.go
  • agent/weknora/weknora_agent.go
  • agent/weknora/weknora_agent_test.go
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/phase2-agent-error-event-redaction

Comment @coderabbitai help to get the list of available commands.

@XnLemon
XnLemon force-pushed the codex/phase2-await-reply-error-redaction branch from 948d294 to cc081c0 Compare July 11, 2026 13:38
@XnLemon
XnLemon force-pushed the codex/phase2-agent-error-event-redaction branch from d606a22 to 7e52085 Compare July 11, 2026 13:38
@XnLemon
XnLemon changed the base branch from codex/phase2-await-reply-error-redaction to main July 13, 2026 02:23
@XnLemon
XnLemon force-pushed the codex/phase2-agent-error-event-redaction branch from 7e52085 to 66f0ebf Compare July 13, 2026 02:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants