2.4.0

• Fix Slack browser auth when more than a single workspace exists.
• Fix Dropbox api credentials check.
• Introduce the daily usage counter.
• Prepare an openclaw-specific version of SKILL.md.
• Update the README (transition to skills.sh as the primary means of installation).

2.3.0

• Document skills.sh as the primary means of installation.
• Make the skill compatible with OpenClaw.
• Properly react to a missing graphical environment when listing services.
• Add a curl invocation example in Telegram's service info command.

2.2.1

• Gracefully deal with a missing encryption key.
• Detect a missing graphical environment.

2.2.0: Merge pull request #32 from imbue-ai/dev

• Add affordances to improve API discoverability.
• Improve instructions for the agents.
• Add basic support for Coolify and Umami.
• Use atomic writes to prevent data corruption.
• Bring the README up-to-date, update the demo recording.

2.1.0

• Introduce latchkey services register.
  • This can be used to:
    • Manage credentials for self-hosted instances of known services (such as GitLab).
    • Add basic support for new services at runtime.
• Sort the output of latchkey services list alphabetically.

2.0.0

• Added basic support for multiple new services (AWS, Gitlab, Telegram, Figma, Google Analytics, Google Directions, Sentry, Stripe, Calendly, Yelp, Zoom).
• Fixed a bug that could result in irrecoverable corruption of stored credentials when the system keyring temporarily required the user to re-authenticate.
• Added a new mechanism for services that cannot express credentials in the form of static curl arguments (latchkey auth set-nocurl).
• Replaced the LATCHKEY_STORE, LATCHKEY_BROWSER_STATE and LATCHKEY_CONFIG with a single LATCHKEY_DIRECTORY environment variable.
• Introduced a basic migration mechanism for stored data.

1.0.1

• Make sure the relevant data is always stored encrypted.
• Add a helper script for the development of new services.

1.0.0

• Latchkey is now primarily a tool to manage API credentials and seamlessly inject them into agent requests.
• Browser logins are just one of (potentially many) sources of those credentials.
• We now support direct insertion of credentials, too.
• Data are always stored encrypted, without exceptions.

0.2.0

• Implement latchkey info.
• Add basic support for Google Workspace and Notion.