Markdown checkboxes written directly in the Task Description (- [ ]) behave like plain text. Checking them does not affect the Task Progress Bar, and they are not exposed through the API as structured checklist items.

Problem:

Many users keep a lightweight “definition of done” or short to-do lists inside the Description because it’s cleaner than creating separate Subtasks or formal Checklists. But since these checkboxes are not recognized as checklist items:

• progress tracking is lost,

• automations (Make/Zapier/API) can’t detect checkbox state without parsing raw markdown,

• the UI and API become inconsistent.

Suggested Solution:

1. Progress Integration

Treat markdown checkboxes as first-class checklist items and optionally allow them to contribute to the task’s progress bar (configurable in ClickApps).

2. API Exposure

Expose description checkboxes in the task API response (e.g., a description_checklist array) so tools can read/write their state without text scraping.

3. Two-way Sync

Checking a box in the UI should update the markdown, and editing the markdown should update the underlying checklist state—similar to GitHub task lists.

This would make simple “inline checklists” fully functional, trackable, and automation-friendly without forcing users to create separate checklist objects.