Collection following & API key controls

Our previous update introduced reusable agent skills and collections. This update adds collection following, collection management from the terminal, and more control over the API keys your tools use.

Follow collections on your machines

Choose Follow collection on a machine to include a collection's current and future published skills. When you add another published skill to that collection, the machine picks it up the next time you run ctxme skills sync, subject to the usual installation checks and confirmation.

You can still use Add current skills for a one-time selection of the collection's current members. Following is an explicit choice, and installation happens when you run sync.

If you deselect a skill from a followed collection, that choice is remembered for its destination on that machine until you restore it. Unfollowing a collection or removing one of its members leaves existing selections and installed files in place. Your version pins and existing install settings stay intact too.

Manage collections from the terminal

The ctxme skills collection commands let you create and rename collections, add or remove members, and preview what applying a collection would add to your registered machine.

For example, to add the current members of a collection called Development to both .agents and .claude:

ctxme skills collection preview "Development" --install-path both
ctxme skills collection apply "Development" --install-path both
ctxme skills sync

Applying the collection saves the machine's selections; sync installs them. You can also follow and unfollow collections, list remembered exclusions, and restore excluded skills from the terminal. Update your CLI before using the new commands.

Choose API-key permissions and expiry

When creating a key in Settings, choose Read only or Read and write, then set its expiry. The default is a read-only key that expires after 30 days. You can choose a custom date and time, or explicitly select Never expires. A fixed expiry stays fixed when the key is used.

Each key also shows Last used, giving you more information when deciding which keys to keep or revoke. Recording starts with this release, so older activity appears as Not recorded until the key is used again. Timestamps may lag recent use by a few minutes; browsing the web app does not count as API-key use.

CLI environment-variable note

If you override the CLI's API key for local testing, use CTXME_CLI__API_KEY. The old CLI__API_KEY name still works as a deprecated alias and prints a notice. Update your shell configuration or scripts to the new name, and avoid setting the two names to different values, which stops the command.

The override is read from the process environment, not .env files, and does not replace your stored keychain credential.