OH MY PM v0.3.1
OH MY PM v0.3.1
Stable patch release for the v0.3 line. It adds two CLI usability improvements
and changes nothing else. There is no schema, store-format, or MCP capability
change, and no behavior change to any existing command.
This release fixes:
- Issue #2 — the CLI had no conventional
--helpoutput. - Issue #3 — installed users had to configure MCP integration by hand.
Included
- Conventional CLI help —
oh-my-pm --helpandoh-my-pm -hprint bounded,
deterministic help to stdout and exit0. Help lists the real current commands
and namespaces, short usage examples, the output modes, and the controlled
exit-code meanings. Namespace and command help is available in the same form,
includingoh-my-pm memory --helpandoh-my-pm providers --help. - Installed MCP client configuration —
oh-my-pm mcp-configprints a generic
stdio MCP client configuration for the installed MCP server. It supports
--json(default),--markdown,--name <name>, and--help/-h.
Help behavior
- Exits
0, writes to stdout only, writes nothing to stderr. - Ends with exactly one newline and is byte-identical across repeated runs.
- Performs no network access, creates no file or application-data directory, and
reads no token. - Unknown commands and options keep their existing nonzero usage exit code.
mcp-config behavior
- Resolves the installed sibling
oh-my-pm-mcpexecutable from the actual
installed location, so installed users never pass--prefix. - Emits an absolute command path with
args: []. - Works on POSIX and Windows, including the Windows
.cmdshim. - Follows a relocated install prefix instead of embedding an install-time path.
- Writes no MCP client file and no project file, and performs no network access.
- Contains no token, credential, environment value, project root, provider
response, or hidden state. - Uses controlled exit
2for an invalid argument or a missing installed
executable, and produces newline-terminated deterministic output. - Markdown output describes exactly the eleven read-only tools, including
project_changes.
Not changed
- No schema change. Project Brain schema stays
1. - No store-format change. Project Memory store format stays
2. - No MCP capability change. Exactly eleven read-only MCP tools in the same
fixed registration order; zero write tools; stdio only; the protocol, tool
order, tool count, and capabilities are untouched. - No memory surface change. Exactly the six memory subcommands.
- No change to existing command semantics or output.
- No new provider, alias, profile, or telemetry.
- No registry publication. All workspace packages remain private.
Safety
- Project files are never modified.
- Memory writes only through explicit CLI
--apply. - The MCP server performs no Project Brain writes.
- No telemetry, no context upload, no network in the memory or help paths.
- Tokens are environment-only — never persisted, printed, or stored. Neither
help normcp-configreads or prints a token.
Compatibility
- Node.js 20+ (the installed runtime baseline; unchanged).
- Windows, macOS, and Linux.
- Project Brain schema 1.
- Project Memory store format 2.
- Fully compatible with a
v0.3.0installation: no migration is required.
Lineage
This patch builds on the immutable stable v0.3.0 release (tag target
0d6f9b1c66ac01835e5f7bf2c8512b5beea50014), which remains immutable and
unchanged. The immutable v0.1.0, v0.2.0-rc.1, v0.2.0, and v0.3.0-rc.1
releases are likewise unchanged.
MCP surface
Eleven read-only MCP tools over stdio, in exact registration order — identical to
v0.3.0:
project_brief
project_risks
project_next
project_handoff
github_project_brief
github_project_risks
github_project_next
github_project_handoff
provider_status
github_provider_diagnostics
project_changes
Assets
oh-my-pm-v0.3.1.tar.gz
oh-my-pm-v0.3.1.zip
oh-my-pm-v0.3.1-SHA256SUMS.txt
Both archives carry the same self-contained "project-brain" profile bundle
(eleven MCP tools, the bundled @oh-my-pm/project-memory package, the six memory
subcommands, Project Brain schema 1, store format 2). They are byte-reproducible
and have equivalent logical inventories.
Getting started
See getting-started-installed.md for
download, checksum verification, preview-first installation, capture, status,
history, changes, export, delete, MCP client configuration, and the explicit
v1 → v2 migration command.