Modal

Modal connects with a token created in your Modal settings. A Modal token resolves to exactly one workspace, so one token connects one workspace. Tokens are encrypted before they are stored, and the agent never sees them.

1. Open Modal, go to Settings → Tokens.
2. Click New token and copy both the token ID (starts with ak-) and the token secret (starts with as-).
3. Paste both values into Polylane.
4. Polylane validates the pair and starts syncing.

Polylane discovers your environments and, within each one, your apps, functions including web endpoints, running sandboxes, volumes, secrets, queues, and dicts. Secrets are mapped by name only: Modal never exposes secret values.

Modal has no read-only token option, so a token carries the permissions of the account that created it. Polylane only reads from Modal during sync.

Troubleshooting

"Invalid token" error

• Both the token ID and the token secret are required; either one alone cannot authenticate.
• Check that the token has not been revoked in Modal's settings.
• Confirm you copied the whole value, including the ak- and as- prefixes.

Missing resources

• Functions are discovered through their app, so an app that has never been deployed has no functions to show.
• Finished sandboxes are skipped: only running ones appear.
• Trigger a manual sync to refresh sooner than the next scheduled pass.

Metrics and cost

• Apps carry two charts: stderr log lines per bucket, and metered spend per hour. Modal reports only instantaneous gauges for everything else, so functions, sandboxes, and volumes have no charts of their own.
• Stderr counts are log lines rather than failures: one Python traceback is several lines.
• Modal keeps logs for 24 hours, so a chart never reaches further back than that.
• Spend is attributed per app, and Modal materialises an hour only once it has ended, so the newest hour reads low until it settles.