What task are you trying to do?
Bring the global typography hierarchy in line with PawWork's positioning as an agent workbench, where users hold more context per screen and stay in longer sessions than in a casual chat tool. Today PawWork is split between 13px (sidebar list, post-#306) and 14px (chat body, composer input, dialogs, settings forms) for no perceivable hierarchy reason. Collapsing 13/14 to a single 13px body, with 14px reserved for hierarchy headers and 12px for code, produces a cleaner scale and lifts effective information density across long working sessions.
What do you do today?
Chat messages and composer input render at 14px via text-14-regular (body) and text-14-medium (hierarchy) utility classes. Code blocks (inline and fenced) inherit the same 14px body. After PR #306 the sidebar moved to 13px while everything else stayed at 14px, so the type scale now carries two adjacent body sizes that look almost the same and split visual rhythm between sidebar and main panel.
What would a good result look like?
A single 13px body across chat, composer, dialogs, settings forms, tool labels, and message metadata. The 14px size is kept only as a hierarchy header for places where weight and size together carry meaning (settings section heads, tool-part titles, chip labels). Code (inline and fenced) renders at 12px so it reads as quieter than prose around it, freeing visual budget for diff highlights, syntax colors, and tool output framing. Hierarchy resolves to: 12 code, 13 body, 14 section header, 16 large title / dialog header, 20 emphasized title, 28 empty-state hero. Settings page h1 (set to 16 in #306) stays at 16.
Which audience does this matter to most?
Both
Extra context
Canonical design covering both this issue and sister issue #315 (sidebar icon scale and alignment polish) lives in the first comment below. Implementation lands as a single PR closing both, since the two changes touch overlapping sidebar files and any sequenced ordering creates phantom diffs.
What task are you trying to do?
Bring the global typography hierarchy in line with PawWork's positioning as an agent workbench, where users hold more context per screen and stay in longer sessions than in a casual chat tool. Today PawWork is split between 13px (sidebar list, post-#306) and 14px (chat body, composer input, dialogs, settings forms) for no perceivable hierarchy reason. Collapsing 13/14 to a single 13px body, with 14px reserved for hierarchy headers and 12px for code, produces a cleaner scale and lifts effective information density across long working sessions.
What do you do today?
Chat messages and composer input render at 14px via
text-14-regular(body) andtext-14-medium(hierarchy) utility classes. Code blocks (inline and fenced) inherit the same 14px body. After PR #306 the sidebar moved to 13px while everything else stayed at 14px, so the type scale now carries two adjacent body sizes that look almost the same and split visual rhythm between sidebar and main panel.What would a good result look like?
A single 13px body across chat, composer, dialogs, settings forms, tool labels, and message metadata. The 14px size is kept only as a hierarchy header for places where weight and size together carry meaning (settings section heads, tool-part titles, chip labels). Code (inline and fenced) renders at 12px so it reads as quieter than prose around it, freeing visual budget for diff highlights, syntax colors, and tool output framing. Hierarchy resolves to: 12 code, 13 body, 14 section header, 16 large title / dialog header, 20 emphasized title, 28 empty-state hero. Settings page h1 (set to 16 in #306) stays at 16.
Which audience does this matter to most?
Both
Extra context
Canonical design covering both this issue and sister issue #315 (sidebar icon scale and alignment polish) lives in the first comment below. Implementation lands as a single PR closing both, since the two changes touch overlapping sidebar files and any sequenced ordering creates phantom diffs.