The work log is a journal of titled notes on a thunk. Use it to record what changed and why — a cutover, a production incident, or a decision that does not belong in the workflow plan.
Only the thunk's Owner and Admins can see or change it. Human Agents and End Users cannot. A public sample thunk does not show its work log to visitors. For the roles themselves, see Users and Access Controls.
Open the work log
Open the thunk.
In the left navigation, choose Admin → Work Log.
The table is newest first. Each row shows who added the note (their avatar and name), the title, a short preview, and when it was added. Click a row to open it. A trash can on the row deletes that note after you confirm.
Add a note
Click Add entry.
Enter a title.
Write the note in the editor. It accepts markdown.
Click Add. The new entry opens.
Edit or delete a note
Click a row to open it. The note is read-only until you click Edit. Change the title or body, then click Save. Click Cancel to discard the edit.
To remove a note, click the trash can on its row or on the open note, then confirm. That cannot be undone.
The work log also records who last edited an entry when that is not the original author.
When a coding agent is in the middle of a unit of work, that note may show In progress for up to an hour. After that it looks like a normal note even if the agent did not close it. Open a note to see Related changes — definition edits the agent made during that unit of work. If the agent began a note and then only ran tests, the section says there are no tagged definition changes. New properties or steps do not appear there until a later edit archives them.
From a coding agent
If you build thunks with a coding agent connected to Thunk.AI, the agent can read and update this same work log, and can open a note for a unit of edits so related definition changes show on that note. It still needs to be the Owner or an Admin of the thunk. See Build thunks with the Builder MCP.