API referenceConsole
Cloud provider
Polylane maps your Convex projects and deployments, reads function logs and metrics to find the function that broke, and writes the fix in your code.

Connect

Connect Convex from the terminal. Pass --help for the flags Convex accepts, plus --no-browser for headless environments.

Terminal
polylane cloud connect --provider convex

How it works

Resources in the context graph

Polylane maps your projects and, in each project, its cloud deployments: production, preview, development and custom deployments, with their region, URL and deployment class. Local deployments run on the machines of your developers, so Polylane does not sync them. Polylane syncs every 15 minutes.

Scoped deploy keys

Sync uses the team access token. To read the logs, metrics or data of one deployment, Polylane creates a deploy key for that deployment with only the permission that the read needs: view logs, view metrics or view data. Polylane deletes the key after the read. Each key also expires after 35 minutes. Its name starts with polylane-ephemeral-.

Anomaly detection

Each deployment gets its own monitor. Polylane reads the function failure rate, the query cache hit rate, the scheduled job lag and the function logs, and compares each series with its usual level. It opens an issue when a change is a real problem.

Polylane monitors only production deployments until you turn on Preview and dev deployments in the account settings. Preview and development deployments stay in the graph either way.

What agents can do

During an investigation, agents read function logs, function metrics (invocations, errors, latency, cache hit rate and scheduled job lag) and the team audit log. Agents can also read your data: list the tables of a deployment with their document shapes, read the newest or oldest documents of a table, and run a one-off query. Convex runs that query as a sandboxed query function, so it cannot write data or reach the network.

Agents can request changes through the Convex Management API. The account is read-only by default, and each change needs safety review and approval before it runs.

Troubleshooting

"Not a team access token" error

  • A project token or a deploy key cannot list the projects of the team. Create the token under Team Settings → Access Tokens.
  • Check that the token is not deleted in the Convex dashboard.
  • Make sure you copied the full token.

Missing resources

  • A project without a deployment shows no deployments until the first npx convex dev or npx convex deploy.
  • Click Sync in the account header to sync before the next scheduled sync.

Disconnecting

Disconnecting does not change Convex. Delete the access token under Team Settings → Access Tokens in the Convex dashboard.

Disconnect

Disconnecting stops every sync and check and deletes the credentials Polylane held. Everything Polylane set up in Convex is removed as well; nothing is left behind.

Terminal
polylane cloud disconnect <id>

Tools

6

Operations agents can perform in threads.

convexApi
Call any Convex Management API endpoint that lacks a dedicated tool
convexGetLogs
Get function execution logs for a Convex deployment
convexListTables
List the tables of a Convex deployment with their inferred document shapes
convexReadTable
Read documents from a Convex table, newest or oldest first
convexRunQuery
Run a one-off read-only query against a Convex deployment
convexQueryMetrics
Query function metrics for a Convex deployment

Supported resources

2

Resource types that show up in your infrastructure graph.

Project
Deployment