Skip to content

feat: expose requester-scoped connection diagnostics - #19

Draft
ishankunam wants to merge 1 commit into
feat/vee-agent-tracesfrom
feat/vee-connection-status
Draft

ishankunam wants to merge 1 commit into
feat/vee-agent-tracesfrom
feat/vee-connection-status

Conversation

@ishankunam

@ishankunam ishankunam commented Sep 30, 2026 •

Copy link
Copy Markdown

Teammates repeatedly ask which connections work, but credential availability alone does not prove access. Add check_connections to perform fixed, read-only credential, identity, MCP, and retrieval checks inside Vee, with service-specific recovery steps.

Slack checks always use the verified requester. Checks never start consent, request private scopes, or substitute another grant. Shared-provider probes are blocked in private-context sessions. Journal configuration is explicitly distinguished from tested connectivity. At most two providers run concurrently.

Stack: #17 → #18: traces → #19: connection status → #20: event/task proposals → #21: announcement drafts.

Validation: 9 diagnostic tests passed, TypeScript check, and whitespace check. No live writes or provider configuration changes.

@vercel

vercel Bot commented Sep 30, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
vee Ready Ready Preview Sep 30, 2026 3:38am UTC

This branch was successfully deployed

1 active deployment
Preview — 4d69cc18 Deployed Sep 30, 2026 by vercel[bot]
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.

1 participant