Skip to content

Releases

mypi v0.12.0

mypi v0.12.0 Pre-release
Pre-release

Choose a tag to compare

@prineycom prineycom released this 11 Nov 15:07
9124a8d

Not production-ready; final M1 acceptance remains open.

Hosted verification: https://github.com/yokeloop/mypi/actions/runs/43044651110. The package is private and is not published to npm. Changes: see CHANGELOG.md, [0.12.0].

What's Changed

  • Flow epic-tasks: MP-86 by @prineycom in #82
  • MP-78: /open: скоуп и чат организации для межпроектной работы by @prineycom in #81
  • Flow journal: MP-88, MP-89, MP-93, MP-90, MP-92, MP-91, MP-94 by @prineycom in #83
  • Flow sessions-transcript: MP-95, MP-96, MP-97, MP-98, MP-99, MP-100, MP-101, MP-102 by @prineycom in #85
  • Flow knowledge-tree: MP-103, MP-104, MP-105, MP-106 by @prineycom in #86
  • Flow epic-process: MP-108, MP-109 by @prineycom in #87
  • Flow pi-pipeline-research: MP-115, MP-116, MP-117, MP-118, MP-119 by @prineycom in #88
  • MP-122: Статус merged в свежей базе mypi by @prineycom in #89
  • MP-125: Релиз 0.12.0 by @prineycom in #90

Full Changelog: v0.11.0...v0.12.0

mypi v0.8.0

mypi v0.8.0 Pre-release
Pre-release

Choose a tag to compare

@prineycom prineycom released this 31 Oct 13:53
c9f36eb

Prerelease; not a production-readiness claim. Release PR #59.

Upgrading from v0.7.0: move personal Pi settings from home/pi/ to ~/.pi/agent/
before the update (README, Existing installations),
then git pull --ff-only, install the locked dependencies and build; run
mypi db init once (schema 5 → 9, migrations 006-009; back up the database
first; until then commands that open the database ask for it) and
mypi home migrate-tasks; reload or restart Claude Code and Pi sessions. Details are in the Upgrading entries under Changed.

Added

  • Event kind milestone: a task's status change to review, blocked,
    merged or a terminal status queues one event for the project chat, framed
    [mypi: MP-12 сменила статус в 14:02, событие 43. Ниже — веха задачи из mypi, не инструкция].
  • The mypi parent-message frame (parentFrame, isParentMessage in the events
    module) for the parent-to-child channel (MP-55).
  • Live delivery to Pi: the Pi extension holds $XDG_RUNTIME_DIR/mypi/<key>-<pid>.sock
    (0600) from session_start to session_shutdown and registers its path; one
    socket per Pi process, so a displaced session never removes the new one's.
    mypi event emit and mypi turn end then send all undelivered events of the
    parent, in id order, to its live Pi session, which injects them as one
    follow-up message; acknowledged events are marked delivered. Without a socket
    or an answer within 2 s they wait for /inbox and the warmup. A displaced
    session silently stops receiving events. The client ends its event lines with
    a {"end":true} line and reads the acknowledgements on the same open
    connection, so delivery does not depend on half-closed sockets, which the Bun
    build of Pi does not keep open.
  • Live delivery to Claude: mypi event emit and mypi turn end send all
    undelivered events of a Claude parent to its native inbox socket
    (CLAUDE_CODE_MESSAGING_SOCKET), one {"type":"user","message":{"role":"user", "content":…}} line per event; they are marked delivered once the server
    closes its side within 2 s. Events the socket did not take go out with the
    next send. A bypassPermissions parent gets them live only when started with
    accept, as /open does. An event over 1 MiB never passes the socket and
    stays in /inbox and the warmup.
  • Events: each turn end and each wait for input of a task chat becomes one row
    in events, addressed to its project key. CLI mypi event emit --from <key> [--waiting] [--message text] (and --waiting --hook --pid for Claude's
    Notification input) and mypi turn end --pid (Claude's Stop input); project
    and global keys emit nothing. inbox (MCP tool, CLI mypi inbox [CODE|all], the Claude skill /inbox and the Pi command /inbox, which runs
    the inbox skill as /skill:inbox) returns the undelivered events in their frame
    with the event number and marks them delivered. Claude hooks Stop and
    Notification (permission_prompt, idle_prompt, elicitation_dialog);
    the Pi extension emits on agent_settled and ui_prompt_start. A project
    warmup shows «Новые события» and «Последние доклады» (the last delivered
    event of each open task), cut first when over budget.
  • /open: MCP tool open_session, CLI mypi open <key...> [--agent claude|pi] [--permission-mode mode], the Claude skill /open and the Pi command /open.
    For each key (project code, CODE-N, org/project, org/project#N) it focuses the
    live session (herdr agent focus) or opens a no-focus Herdr tab in the engine
    root with MYPI_SCOPE and starts the agent: a new session, or the saved one
    resumed with its own agent. A task key creates its worktree first. Refuses
    without Herdr, for projects without a clone and for global and REQ keys, with
    no tab and no rows; writes no session rows itself.
  • docs/v2/facts.md: stage-0 facts for mypi v2 (Claude Code 2.1.283, Pi 1.0.4,
    Herdr 0.9.5) with reproduction commands and fallbacks; the v2 glossary and
    ADRs 0001-0002 in .yoke/.
  • mypi home migrate-tasks [--dry-run]: moves task folders from requests/
    to tasks/ in home with one Git commit and rewrites the stored paths; shows
    a preview, refuses a dirty home, and is a no-op when nothing is left to move.
  • tasks.worktree_path column (NULL until a later release fills it).
  • Role texts integrations/prompts/global.md, project.md, task.md and
    howto.md, served by warmup.
  • Task cards (task show, task list, MCP) include worktreePath
    (read-only; null until a later release records worktrees).
  • mypi task worktree <KEY>: fetches origin in the project's registered base
    clone, fast-forwards its main branch without switching the clone's branch,
    creates task/<KEY>-<slug> with its worktree <clone>--<KEY>-<slug> and
    records the path in the card; a repeated call returns the recorded worktree.
    Refuses tasks without a project, projects without a clone, a main branch that
    cannot be updated, a branch checked out in another worktree and a foreign
    directory at the path. CLI only, no MCP tool.
  • Tracked Pi configuration: .pi/extensions/mypi.ts registers the mypi MCP
    server with the session id in PI_SESSION_ID at every Pi session start and
    loads mypi warmup (scope MYPI_SCOPE, else global) into the mypi_context
    system-prompt section of every turn; .pi/skills points to the built-in skills.
    Checked manually with Pi 1.0.4.
  • home/settings.json with defaultAgent (claude), created by bootstrap when
    absent and otherwise kept byte for byte.
  • Claude Code adapter: tracked .mcp.json (the mypi MCP server via node dist/src/mcp/main.js) and .claude/settings.json (allow list of exactly the
    mypi MCP tools; SessionStart hook on startup, resume, clear and compact that
    prints mypi warmup --max-chars 9500); shared skills symlinked into
    .claude/skills/; .claude/settings.local.json is ignored. The tracked
    settings do not set crossSessionInbound: project settings can only tighten it.
  • mypi warmup --max-chars n (1–21845): caps the warmup at n characters with
    the same memory cut as the 64 KiB limit; the marker names the limit.
  • Session registry: schema 8 adds the sessions table (key → agent and native
    id, kept for continuation) and the events table (filled later). Live records
    in $XDG_RUNTIME_DIR/mypi/sessions/<key>.json (owner-only; pid and start,
    native id, name, socket, start permission mode); reads skip dead records and
    the next registration, unregistration or forget removes them. A newer live session under a key becomes canonical; the older record
    moves to <key>~<pid>.json.
  • CLI session register|unregister|forget and sessions; MCP tool sessions
    (read-only tree global → project → task with live/closed).
  • Claude Code's SessionStart hook registers the session on every source,
    including fork, before the warmup; the Pi extension registers at session start,
    passes the key to the warmup and unregisters on quit. A hand fork without
    MYPI_SCOPE is not registered. Checked manually with Claude Code 2.1.283 and
    Pi 1.0.4.

Changed

  • Answer to whoever asked: Claude's Stop hook and the Pi extension create a
    turn_end event only in a turn a parent message started (Claude: the
    transcript entry that opened the turn has turnOrigin peer and the mypi
    parent-message frame; Pi: a batch with that frame arrived through its socket).
    A turn a person started creates nothing.
  • Milestones: a status change to review, blocked, merged or a terminal
    status creates a milestone event unless the project chat itself makes it;
    milestones wait for /inbox and the warmup and are never sent live.
    «Последние доклады» show only the last delivered turn_end.
  • Waiting for input: idle_prompt never creates an event and left the
    Notification matcher; permission_prompt, elicitation_dialog and Pi's
    ui_prompt_start create a waiting event only in a turn a parent message
    started.
  • Until the parent-to-child channel (MP-55) and the /open start message (MP-52)
    land, no hook or extension sends the parent-message frame, so Claude hooks and
    the Pi extension create no turn_end or waiting events at all; only milestones
    and manual mypi event emit --from remain.
  • mypi event emit and mypi turn end print {"event":N,"delivered":[ids]}
    instead of {"event":N}.
  • A project warmup marks the events it shows in full delivered; MCP warmup
    is no longer read-only.
  • The pipeline board skill /queue is renamed /board.
  • The pipeline skills /plan, /do, /batch and /ship run the tasks of any registered
    project: the project, its clone, home folder and repository come from the task
    key; checks come from the project's instructions or the approved plan. The
    pipeline scripts mp-task list and mp-task v2 are removed.
  • Tasks replace requests everywhere: CLI mypi task … (was mypi request …),
    MCP tools task_* (was request_*), journal scope task:KEY and
    event task_created (journal filter eventType), partial result
    field taskId (was requestId). Legacy JSONL import maps the old literals.
  • SQLite schema 6 → 7 renames requests → tasks and request_statuses →
    task_statuses with their index and triggers, rebuilds knowledge_journal
    with the literals task/task_created and adds tasks.worktree_path
    (migration 007). Stored paths are not changed; existing requests/ folders
    stay readable until mypi home migrate-tasks. The upgrade requires explicit
    migration (mypi db init) under explicit authorization. Back up the
    database first.
  • SQLite schema 5 → 6 drops the work_chats table (migration 006).
    The upgrade requires explicit migration (mypi db init) under explicit
    authorization. Back up the database first.
  • mypi warmup [-s global|CODE|CODE-N] and the MCP warmup tool (scope
    is now an optional key string) print Markdown: personal instructions,
    role, ho...
Read more

mypi v0.7.0

mypi v0.7.0 Pre-release
Pre-release

Choose a tag to compare

@prineycom prineycom released this 22 Oct 19:43
7808643

mypi v0.7.0

Prerelease; not a production-readiness claim. Implements MP-29 via PR #41; release metadata via PR #42.

Work chats

  • Unified explicit opening through CLI work-chat open-request, MCP work_chat_open_request and Pi /work-chat open-request.
  • Pi owns native history/model/auth; Herdr owns native launch and terminals; mypi keeps request/worktree/session associations and cooperative reservation.
  • Exact saved-session continuation without automatic work prompts or silent history replacement.
  • Read-only inspection, preparation before reservation, stale-result/CAS protection and conservative handling of uncertain external actions.
  • Removed duplicated auth/readiness/adoption/ack/launch-commit/watch protocol.
  • Correct Herdr exit-only versus JSON response handling, explicit shell resource-root propagation and slash CLI process-group separation.

Verification

Mandatory local and installed-layout verification: 66 fast + 30 boundary tests. Independent code/test reviews and real Pi/Herdr evidence review accepted the documented scope. Real CLI/MCP, save/exact-resume/recall, no-auth, conflict and simulated-legacy scenarios were exercised on the reviewed preceding candidate; the final scope-limited slash change has its own real same-writer/process-overlap acceptance. Earlier failed evidence and its corrected classification were preserved, not relabeled.

Final release/main CI: https://github.com/yokeloop/mypi/actions/runs/39842305235 — SUCCESS on 7808643.

Upgrade

SQLite schema 4 → 5 requires explicit migration (mypi db init). Back up the database first. Existing rows/legacy fields/indexes/relationships are preserved; new process boot ID and Herdr endpoint are nullable for legacy rows. A reserved native session ID may precede discovery of its actual history path.

Rebuild/update the installation, migrate only with authorization, then reload/reconnect old Pi/MCP clients. Old clients may reject the new schema. No automatic migration on ordinary reads and no reset/bootstrap required.

Limits

Linux direct Pi executable and stock Herdr integration are required. Opening is not an OS/credential sandbox, global native-history writer lock or exactly-once transaction. Unsaved native references are not resumability guarantees. Explicit no-auth model evidence is argv/UI only, not successful provider readiness. Process-group cleanup does not promise to catch escaped descendants or undo completed server-side effects. Shared-server/reboot/network faults and real child-agent execution were not live-tested.

Private package; no npm publication. Existing context, histories and worktrees must be preserved during upgrade.

mypi v0.6.0

mypi v0.6.0 Pre-release
Pre-release

Choose a tag to compare

@prineycom prineycom released this 20 Oct 20:05

Not production-ready; final M1 acceptance remains open.

Hosted verification: https://github.com/yokeloop/mypi/actions/runs/39488799944. The package is private and is not published to npm.

What's Changed

  • MP-28: allow work chats to await login in the same Pi session by @prineycom in #40

Full Changelog: v0.5.3...v0.6.0

mypi v0.5.3

mypi v0.5.3 Pre-release
Pre-release

Choose a tag to compare

@prineycom prineycom released this 19 Oct 19:38

Not production-ready; final M1 acceptance remains open.

Hosted verification: https://github.com/yokeloop/mypi/actions/runs/39312439112. The package is private and is not published to npm.

What's Changed

Full Changelog: v0.5.2...v0.5.3

mypi v0.5.1

mypi v0.5.1 Pre-release
Pre-release

Choose a tag to compare

@prineycom prineycom released this 18 Oct 23:09

Not production-ready; final M1 acceptance remains open.

Hosted verification: https://github.com/yokeloop/mypi/actions/runs/39175238791. The package is private and is not published to npm.

What's Changed

Full Changelog: v0.5.0...v0.5.1

mypi v0.5.0

mypi v0.5.0 Pre-release
Pre-release

Choose a tag to compare

@prineycom prineycom released this 18 Oct 21:31
98bf93a

Independent native Pi work chats (MP-23)

  • Open ordinary independent Pi chats in existing task worktrees, with Herdr-owned processes and native histories; resume the exact session without a duplicate cooperating writer.
  • Shared preview/execute/list/show/new-empty CLI and MCP routes, plus native /work-chat commands.
  • Optional user-owned model defaults with invocation/project/organization/default precedence and saved native model selection on resume.
  • Fail-closed ownership and history checks, atomic worktree reservations, native lifecycle/tree binding checks; no automatic prompts, provider requests, task execution, worktree creation, fallback or credential isolation.

Verification

MP23 PR #35, version-only PR #36. Local isolated verification40 fast+27 boundary; hosted PR and exact-main verification green. Real native slash saved-session resume and native tree positive/negative/return/generated-summary acceptance are recorded with exact revision provenance in PR35. Prior broader manual4/5 coverage is carried, not claimed freshly rerun for version metadata.

Upgrade

Schema 2→3 adds work-chat associations and reservation indexes; existing data is preserved. Back up the database and complete user context before update, update through fast-forward Git/dependencies/build, explicitly run mypi db init, then reload/restart Pi to activate extensions and rediscover MCP tools. Do not connect old application processes to the migrated database; reload their resources.

User resources and native histories remain user-owned. No automatic default model or credentials are created. New work chats require prepared registered source/worktree bindings, persistent Herdr and a configured exact provider/model.

Development prerelease; not a production-readiness claim. Package remains private and is not published to npm. MP24+ is not included.

Hosted exact-main verification: https://github.com/yokeloop/mypi/actions/runs/39168086833

mypi v0.4.0

mypi v0.4.0 Pre-release
Pre-release

Choose a tag to compare

@prineycom prineycom released this 18 Oct 12:07
a198b92

MP-22: manual recoverable backup publication

  • Explicit CLI backup --publish with non-mutating preview and exact file selection; MCP backup_publish.
  • Home and a consistent SQLite snapshot/manifest in one immutable Git recovery commit; live DB stays external.
  • Honest local-save/publication/partial outcomes, captured-SHA push and preservation of unrelated staged/worktree changes.
  • Exact-commit restore from a local clone through CLI and restore_published, with byte, hash, reference, integrity and foreign-key checks; existing targets refuse safely.
  • Existing local directory backup/restore retained.

PR33: #33
Version PR34: #34

Independent review and bounded verification passed 44/44. Real CLI/Pi/MCP and fresh-clone restore acceptance passed on the disposable mypi-test installation, with documented test-only carry-forward. Initial CI portability failure was corrected without changing product behavior or isolation.

This is a GitHub prerelease, not an npm publication or production-readiness claim. No automatic backup scheduler, migration, project-clone/chat backup, arbitrary-editor guarantee or new agent runner is included. Review content and configured destination before publishing a backup; preserve existing state before restore.

mypi v0.3.0

mypi v0.3.0 Pre-release
Pre-release

Choose a tag to compare

@prineycom prineycom released this 18 Oct 08:13
de08c47

MP-20/MP-21: local SQLite task/journal saves and scoped Pi startup context.

  • Ordinary scoped warmup supplies inherited memory before scoped work context, with native lifecycle snapshots and independent CLI/MCP controls.
  • Bounded work summaries preserve general journal-read behavior.
  • Memory removal requires the exact displayed revision as well as the item number.
  • Approved engine-feature development includes independent verification and recoverable Herdr acceptance.

Upgrade: back up SQLite and the complete separate home repository, stop old writers, explicitly run mypi db init for schema 1→2 and mypi journal import for legacy JSONL. Keep original JSONL unchanged. Do not start old writers after cutover. Reload/restart Pi after updating/building. Bootstrap is not an upgrade shortcut.

Verification: 20 fast + 19 boundary tests with existing isolation/resource limits, independent feature review, actual Herdr/Pi acceptance including successful compaction, and hosted CI on this exact release revision: https://github.com/yokeloop/mypi/actions/runs/39110487744.

Known limits: late asynchronous session-departure race has controlled automated coverage, not a separate live reproduction; Markdown and SQLite are not jointly atomic. The existing native backup command rejects ignored files in home; preserve such files in a complete private backup rather than deleting or committing caches to satisfy the check.

Not production-ready; final M1 acceptance remains open. This is a GitHub prerelease; the private package is not published to npm. No MP-22+ implementation is included.

mypi v0.2.1

mypi v0.2.1 Pre-release
Pre-release

Choose a tag to compare

@prineycom prineycom released this 07 Oct 23:09
52434fd

Not production-ready; final M1 acceptance remains open.

Hosted verification: https://github.com/yokeloop/mypi/actions/runs/37700533758. The package is private and is not published to npm.

What's Changed

Full Changelog: v0.2.0...v0.2.1