Skip to content

counterparts 0.3.53

Choose a tag to compare

@mlapeter mlapeter released this 10 Nov 14:30
· 319 commits to master since this release

Your page names what it sets down and tells more than corrections; the morning wake reads cleaner; things waiting on you come up when they're relevant, not as a pile. What you'll notice: the morning after a night's page write, the wake can say "Set down from my page last night: …"; the wake ends with a "Carried forward" line, gives overdue items as a count with the oldest date, and names the session id in its first line; and now and then a line "Waiting on , ask when it fits: …" when something you owe an answer on comes up in the conversation or at the week's session start. The wake changes are in the shaped wake (on for a store created since 0.3.46, or after counterparts wake-shape on). remember takes story: true. No store-format change (store v15, cache v7), no migration. Nothing to run after upgrading beyond the usual restart of the dashboard and every Claude Code session. Going back to 0.3.52 is a reinstall with no store restore: counterparts disconnect, 0.3.52's install, then counterparts connect.

  • The page says what it sets down. The self page stays within its room, so each night a new line pushes an old
    one out. Now the night's page writers name the lines they take out, with a short why, and anything taken out
    that wasn't named is recorded anyway; a line only reworded, or folded into a story still on the page, isn't
    counted as gone. Each line set down is kept as a memory, word for word. The next morning's wake names up to two
    ("Set down from my page last night: …"), and recall "set down" lists them all, newest first, with why and date.
    When life brings one up again (it's used, or a newer memory says it again), the night's writers are shown it and
    may put it back.
  • The page's stories are about growth, not only corrections. On a store that keeps its page in its own form
    (counterparts page-form own), the night's page writers are told to keep a mix of story kinds (corrections that
    changed how the counterpart works, and also what went right, discoveries, and moments with the owner), and that a
    story earns its place if it would still teach something in a different project. Day's end is shown the day's
    memories about me or us with a small head start over the day's work, so a busy work day doesn't crowd them out.
    A practice on the page that is only about the work may move into a skill memory, which recall brings back when
    the work calls for it; the set-down record names it. On every store, remember takes story: true to nominate a
    moment as a story: the night's writer sees it first and still decides, and one it passes by fades like any
    other memory.
  • The wake says what it points at, once. A reminder told in another session is listed again by title instead of
    "shown earlier", which that session never saw. The night's closing line no longer repeats a sentence the page or
    day's end already says, and the same line on a second morning shrinks to a clause. Overdue items get their own count
    with the oldest date. A handoff waiting on an answer with nothing new sinks below the others, and one more than a week
    old that nothing refers to stops being listed (still under recall "handoffs"). Every line under Elsewhere says when.
    "Last said" quotes a whole first sentence when it fits. "Last night" stops saying the run is under way once the
    dream is written up. And the wake's first line names the session id, which the reflect tool asks for.
  • What waits on you comes up when it's relevant, not as a pile. An item waiting on your answer is no longer one of
    the wake's still-open lines. Instead, when a turn you start touches one, it's raised once after the recall block,
    with what it needs and how long it has waited; and a session's wake says at most one ("Waiting on , ask
    when it fits: …"), the most relevant to the folder's week first, the same item there at most once a week. Each item is raised at most once a lived day across
    every session, then again after 3, 7 and 14 lived days, and then it's parked (still under recall "still open").
  • "PW" before a version number is no longer read as a password. 0.3.52's prose-password check redacted the
    version in "PW 1.48" (short for Playwright); a bare Playwright version after "PW" is now left alone, and short
    passwords after "PW" are still redacted. The manual and README say "most passwords" named in a sentence.