chan1103
c2456d882f
Addresses the fourth review round (Codex no-email finding on d37e3992c, confirmed and scoped by internal review): - resolveProviderCredentialIdentityKey: the anthropic org qualifier now rides on whichever base identity exists (email > account > project), not only email. The account UUID is identical across the orgs of one login account, so the bare account fallback let a second subscription replace the first whenever the email could not be recovered (token response omits it AND bootstrap fails). Org-only credentials key on the org alone instead of losing identity entirely. - matchesReplacementCredential: the one-way legacy claim strips a trailing |org: from ANY anthropic base key (account/project included); only anthropic keys carry the qualifier, so other providers are unaffected. - Usage-report dedupe falls back to the org-qualified account for no-email anthropic reports instead of returning no identifiers. - Broker report/overlay routing (matchUsageReport/findMatchingReportIndex) is org-decisive on EITHER side: an org-less legacy credential no longer receives an org-attributed sibling's pool via the lone-candidate or email/account fallback, and an org-less overlay only merges into org-less reports. - omp usage unreported-account attribution follows the same either-side rule, so a legacy row whose fetch failed surfaces as 'no usage data' instead of being hidden by a sibling's report. - Regression tests: no-email identity coexistence/replace/claim, no-email report dedupe, org-less broker routing, either-side unreported attribution.
@oh-my-pi/pi-coding-agent
Core implementation package for the omp coding agent in the oh-my-pi monorepo.
For installation, setup, provider configuration, model roles, slash commands, and full CLI reference, see:
Package-specific references:
Memory backends
The agent supports three mutually-exclusive memory backends, selected via the memory.backend setting (Settings → Memory tab, or ~/.omp/config.yml):
off(default) — no memory subsystem runs.local— existing rollout-summarisation pipeline; writesmemory_summary.mdand consolidated artifacts under the agent dir.hindsight— talks to a Hindsight server (Cloud or self-hosted Docker), retains transcripts every Nth user turn, recalls memories on the first turn of a session, and exposesretain,recall, andreflect.
Hindsight quickstart
- Run a Hindsight server (Cloud or
docker run -p 8888:8888 ghcr.io/vectorize-io/hindsight:latest). - Set
memory.backend = "hindsight"andhindsight.apiUrl = "http://localhost:8888"(or your Cloud URL). - Optional environment overrides (env wins over settings):
HINDSIGHT_API_URL,HINDSIGHT_API_TOKEN— connectionHINDSIGHT_BANK_ID,HINDSIGHT_DYNAMIC_BANK_ID,HINDSIGHT_AGENT_NAME— bank addressingHINDSIGHT_AUTO_RECALL,HINDSIGHT_AUTO_RETAIN,HINDSIGHT_RETAIN_MODE— lifecycleHINDSIGHT_RECALL_BUDGET,HINDSIGHT_RECALL_MAX_TOKENS— recall sizingHINDSIGHT_BANK_MISSION,HINDSIGHT_DEBUG
Switching backends mid-session is honoured on the next system-prompt rebuild and the next /memory slash command. Existing users with memories.enabled = true|false are migrated to memory.backend = "local"|"off" exactly once on first launch.