When a task description is created or updated through the API (markdown_content), tables are rendered with default column widths that have nothing to do with the content. Short columns (dates, amounts) waste space, and the table is much wider than it needs to be.

There is currently no way to control this: markdown has no syntax for column widths, the API returns and accepts the description only as plain text or markdown, and even in the UI there is no "fit to content" option - only manual dragging of column borders or "fit container" (full width, equal columns).

Requests: 1) an "auto-fit columns to content" option for tables (UI), ideally as the default for tables created from markdown; 2) a way to set table column widths through the API, e.g. an optional parameter on task create/update (auto-fit / full width) or support for a width hint in markdown/HTML tables; 3) optionally, access to the rich-text (delta) format of the description via the API, so integrations can read and write tables with their layout.

Use case: we generate task descriptions automatically (accounting summaries with an 8-column table of invoices and amounts) and every time someone has to resize the columns by hand.