Convex integration. Find the Convex function that broke from its logs and metrics.
Praxen Inc. maps your Convex projects and deployments, reads function logs and metrics to find the function that broke, and writes the fix in your code.
Get started for freeHow to set up Convex
The checked guide does not publish an end-to-end setup duration. Discovery begins after token validation.
- Open Convex Dashboard → Team Settings → Access Tokens and create a team access token.
- Paste the complete token into Convex’s connection form in Praxen Inc. A project token or deploy key cannot list team projects.
- Connect after validation. One token connects one team; inspect each project and its cloud deployments in the account.
Permissions and access
Team access tokens grant team management access; there is no read-only team token selector in the Praxen Inc. flow. Inventory reads projects and deployments. Log and metric reads mint a short-lived deploy key scoped to that read, use it for one call, then delete it. The connection therefore needs management capability even though those investigation calls read telemetry.
Discovery, refresh and the connected view
Projects and cloud deployments refresh every 15 minutes, including production, preview, development and custom deployment classes with their URLs and regions. Local deployments on developer machines are deliberately excluded. Function logs and deployment metrics are read through investigation tools; audit logs require a paid Convex plan, and free teams fall back to logs and graph context.
Disconnect and revoke access
Disconnect the team in Praxen Inc., then delete the team access token in Convex Dashboard → Team Settings → Access Tokens. Use manual Sync while connected to pick up a newly deployed project sooner.
Provider credentials and Praxen Inc.’s access mode are separate. Where write-capable tools exist, the connected account’s Settings page offers a Read-only switch. Turning it off permits writes subject to review and confirmation, but cannot add permissions to the provider credential. Agent-connected Kubernetes clusters stay read-only.
In the graph.
Every Convex resource Praxen Inc. picks up sits in the graph with its connections, config and history.
Project Deployment Convex tools.
The calls Praxen Inc. can make to Convex when it looks into an issue.
Convex -
convexApiCall any Convex Management API endpoint that lacks a dedicated tool -
convexGetLogsGet function execution logs for a Convex deployment -
convexListTablesList the tables of a Convex deployment with their inferred document shapes -
convexReadTableRead documents from a Convex table, newest or oldest first -
convexRunQueryRun a one-off read-only query against a Convex deployment -
convexQueryMetricsQuery function metrics for a Convex deployment
Convex setup and troubleshooting
Common questions.
How does Praxen Inc. connect to Convex?
Open Convex Dashboard → Team Settings → Access Tokens and create a team access token. Paste the complete token into Convex’s connection form in Praxen Inc. A project token or deploy key cannot list team projects. Connect after validation. One token connects one team; inspect each project and its cloud deployments in the account.
What does Praxen Inc. sync from Convex?
Projects and cloud deployments refresh every 15 minutes, including production, preview, development and custom deployment classes with their URLs and regions. Local deployments on developer machines are deliberately excluded. Function logs and deployment metrics are read through investigation tools; audit logs require a paid Convex plan, and free teams fall back to logs and graph context.