You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rewriting a bullet list no longer breaks follow-up edits. When the project agent rewrote a
list, table, or other container, every item inside it silently lost its internal identity. A
follow-up edit on one of those items then failed and triggered repeated repair attempts. Items now
keep their identity across a rewrite.
Adding content to a list produces a proper list item. Inserting next to a bullet point could
place a plain paragraph inside the list, which turned into a bullet with a changed block type the
next time the field was opened. Content is now placed as a real list item.
Turning a paragraph into a bullet point keeps it editable by the agent. Using the bullet
button on a paragraph the agent was working with no longer detaches it from the conversation.
Replacing a heading with several paragraphs no longer corrupts the heading. The replacement
paragraphs previously ended up nested inside the heading. They are now placed as proper sibling
blocks, and the heading's position keeps its identity.
Edits that cannot be applied are reported instead of silently emptying a field. Replacement
content that could not be interpreted used to clear the section while reporting success; the field
is now left untouched and the agent is told.
Repeated edits in one request can no longer target the wrong block. When a single request
inserted two blocks under the same temporary name, a later edit in that request could hit the
wrong one. Ambiguous and already-deleted references are now rejected.
ποΈ Improvements
Identifiers assigned to newly inserted blocks are now derived from the block itself, so they can
be recovered if they are ever stripped β newly created sections stay addressable for the rest of
the conversation.
Section identity is now resolved consistently in the editor and in the backend, using the same
rule about which blocks can carry an identity.
π Notes
No database migration is introduced by this release.
Existing projects and work-package descriptions require no manual changes.
Completes the section-identity work started in v1.35.3 and v1.35.4.