PR Custody

feat: proactive Slack notification for auth failures (INT-1442)

@AgentWrapperchecks n/achecks…feat/INT-1442 → next12 files · +423 −8updated 3mo ago

▸Description · 1 noise

Why

29% of create-app runs produce 0 new actions. In 92% of those cases, every endpoint fails CurlTesting due to bad/expired/misconfigured credentials. Users currently get no actionable feedback — they see a generic failure with no guidance on how to fix it.

What

Add is_auth_issue detection to CurlTester (state.py, prompt.py, agent.py) — flags 401/403/auth keyword failures
Add compute_is_auth_issue() on CurlTesterResult — True when ALL failures are auth issues
Add early exit in CreateApp when curl auth detected → returns is_auth_issue=True
Add FAILED_AUTH_ISSUE notification branch in dispatcher — sends user thread + internal channel alerts
Add notify_auth_issue_in_slack_thread() — user-facing Slack message with fix instructions and dashboard link
Add notify_auth_issue() — internal channel notification with workflow details
Re-export new functions from common/utils.py
Add 17 tests across 3 new test files

How to Test

# Run all new tests
uv run pytest cortex/tests/test_agents/test_curl_tester/test_auth_issue.py common/tests/test_slack_utils.py cortex/tests/test_dispatcher_auth_notify.py -v

# Verify formatting/linting
make fmt && make chk

Pre-Review Checklist

I have self-reviewed this PR

Notes

Depends on PR #1249 (feat/INT-1435) which adds the base is_auth_issue field — but the field definition is included here for self-containment
Pyrefly fails in CI for worktree-based checkouts (pre-existing issue with **/.[!/.]*/**/* exclude pattern matching .worktrees path) — not related to this PR
The FAILED_AUTH_ISSUE enum value and DB migration already exist on next

▸ 1 bot/status comment hidden

@linear[bot]3mo ago

Context

From Slack thread, team member requested:

"is it possible to make this agent proactive? send a message on slack whenever something like happens and wait for user to fix it by creating new connection, adding scopes and all"

Currently when CurlTester detects auth failures, the pipeline short-circuits silently (PR #1249). No notification to the user.

What to do

When is_auth_issue=True detected by CurlTester, send Slack notification
Include: app name, which connection failed, error details, instructions to fix
Consider webhook or Slack bot for delivery
Optionally: allow workflow to pause and resume after user fixes credentials

PR #1249 adds is_auth_issue detection
29% of runs produce 0 actions, 92% due to auth
Would reduce wasted compute and speed resolution

loading diff…

feat: proactive Slack notification for auth failures (INT-1442)

Why

What

How to Test

Pre-Review Checklist

Notes

Context

What to do

Related

Why

What

How to Test

Pre-Review Checklist

Notes

Context

What to do

Related