Known limitations

ToDoddle is in active development. Current boundaries include:

• Direct Messages are one-to-one. Multi-participant conversations are not yet available.
• Browser push needs a supported browser and workspace push configuration. iPhone and iPad push also requires ToDoddle to be installed on the Home Screen.
• Website search is case-insensitive database substring matching in one workspace. It has no typo tolerance, semantic ranking, or cross-workspace search. MCP project search is bounded to one granted project.
• Local stdio MCP is generally available. Hosted Streamable HTTP MCP is a private alpha for approved users and clients. Clients must be pre-registered or use a metadata document from a trusted HTTPS origin; it is not public self-service.
• Agent claims coordinate one ticket at a time. Project queue roles, capabilities, eligibility rules, and post-run recipes are project-wide. Per-ticket routing rules remain unavailable.
• Cross-board ticket moves stay inside one project; cross-project moves are unavailable.
• Context comments accept pasted or dropped files as links to project documents. They do not have a separate attachment list.
• Support and Testbench are not available on Free or Hobby. Custom portal domains and paid badge removal require Business or Enterprise. The Testbench home page does not list public projects.
• Free workspaces cannot upload or stream video. Video delivery is measured for paid workspaces, but ToDoddle currently warns instead of stopping uploads or playback at the monthly allowance.
• Enterprise is not self-service and has no published service or governance commitment.

These limits are not permission shortcuts. Existing workspace, project, file, billing, and Agent Connection access checks still apply. Prefer the documented workaround and track a feature request rather than building an unsupported process around an incidental behavior.