Config descriptions, smarter API keys, fast-agent defaults, and one-time-use data

The API Keys table in Settings → API now shows a "Last used" column for each key, so you can spot stale or active keys at a glance. Org admins can also now create service keys – choose org-wide or project scope and set read or write permissions – without leaving the dashboard. Personal key management (create and revoke) works the same as before.

Project configs (Settings → Project → Configs) now have an optional Description field, placed directly below the config name. When the assistant needs to decide which login to use for a test, it reads that description alongside the name. A note like "Use for privately-paying patients; don't use for regionally-funded flows" is now enough – you don't need to mirror the same guidance into Assistant Rules. The same context is available to the test agent when it runs, so the right credentials are chosen consistently across both chat and scheduled runs.

When you add a test case, the agent picker shows "Fast (default)" – you no longer need to select it manually. Any test created before this change keeps whatever agent it was already using. Fast tests are typically quicker to run; switch to Intelligent in the test editor if a particular flow needs deeper reasoning.