Clankee
Login
Reference

Current limitations

Honest list of Coming soon features, constraints, and unverified behavior.

This page lists constraints and incomplete areas inferred from the product. It is meant to set clear expectations.

Coming soon or unavailable

AreaStatus
In-product docs link on marketing siteComing soon (this Help Center at https://docs.clankee.ai replaces that need)
Slack workspacesComing soon
Microsoft Teams workspacesComing soon
Social login (Google/GitHub/Slack) for Clankee accountsNot available (Discord login is available)

Product constraints

  • Registration may be disabled in favor of a waitlist (email and Discord register).
  • Personal teams cannot be deleted.
  • Team Admins can invite but cannot change/remove members.
  • Brain requires project update permission and the team plan capability brain.
  • Custom team AI providers require the custom_models plan capability.
  • Found knowledge is hidden in the knowledge base list until you filter by type.
  • Brain is read-only and may show a capped number of chunks.
  • System tasks cannot be edited or archived.
  • Schedule timezone is taken from the browser; there is no timezone picker.
  • No in-app notification center; task alerts go to Discord, and app actions use toasts.
  • Discord bot invite confirmation in onboarding is self-attested (“I've added Clankee”).

Marketing vs product surfaces

The marketing site describes proactive “heads-up” style monitoring. There is no dedicated in-app alerts product surface comparable to Tasks, Knowledge, or Workspaces. Prefer documenting Tasks, Discover, chat, and notifications for day-to-day ops work.

Notes and Assumptions

These items could not be fully verified as end-user guarantees from the application UI alone:

  1. Email verification enforcement
    Verification screens and routes exist, but whether every account is forced to verify before using the app can depend on deployment configuration. Follow any verification prompts you see.
  2. Discord gateway behavior
    Chat replies depend on the Discord bot being present and able to reach Clankee. Exact bot permissions beyond the invite flow are not fully configured inside the web UI.
  3. Provider catalogs
    Which integrations appear depends on what is published in the catalog for your environment. Docs use examples shown in marketing/product copy (Notion, Gmail, Drive, GitHub, Linear, Salesforce, and others).
  4. Proactive heads-up alerts
    Marketed as a capability; treat scheduled tasks, Discover, and Discord notifications as the concrete controls available today.

If behavior differs in your workspace, trust the live product labels and contact Clankee support or your admin.

Copyright © 2026