imbue-mngr-pi-coding-usage 0.1.0__py3-none-any.whl

imbue/mngr_pi_coding_usage/plugin.py

@@ -0,0 +1,67 @@
+"""pi usage data provider for `mngr usage` (reader + writer gate).
+
+pi loads exactly one explicit extension -- mngr_pi_coding's lifecycle extension,
+launched with ``pi -e`` -- so the usage *writer* lives there (it already holds
+each assistant message's cost + tokens). This package owns the two pieces that
+are genuinely usage-specific:
+
+1. A gate marker, provisioned per pi agent, that tells the lifecycle extension to
+   emit usage events. Without it the writer stays inert -- so usage events are
+   only written when *this* package (which ships their reader) is installed.
+   Emitting them unread would let ``mngr usage`` fall back to the wrong
+   (process-cumulative) strategy and undercount pi's per-message events.
+2. The reader: an ``aggregate_usage_source`` hookimpl claiming the ``pi-coding``
+   source, aggregated session-incrementally (pi reports cost per message).
+"""
+
+from __future__ import annotations
+
+from imbue.mngr import hookimpl
+from imbue.mngr.config.data_types import MngrContext
+from imbue.mngr.hosts.host import get_agent_state_dir_path
+from imbue.mngr.interfaces.agent import AgentInterface
+from imbue.mngr.interfaces.host import OnlineHostInterface
+from imbue.mngr_pi_coding.plugin import PiCodingAgent
+from imbue.mngr_usage.api import aggregate_session_incremental
+from imbue.mngr_usage.data_types import UsageEvent
+from imbue.mngr_usage.data_types import UsageSnapshot
+
+# Gate marker the lifecycle extension checks (existsSync) to decide whether to
+# emit usage events. Kept in sync with mngr_pi_lifecycle.ts (literal "pi_emit_usage").
+_USAGE_GATE_FILENAME = "pi_emit_usage"
+
+# Source the pi writer emits under ($STATE_DIR/events/pi-coding/usage/...); the
+# reader strips "/usage". A fixed harness id (not the agent subtype), so usage
+# from any pi subtype lumps under one source. Kept in sync with mngr_pi_lifecycle.ts.
+_PI_USAGE_SOURCE_NAME = "pi-coding"
+
+
+@hookimpl
+def on_after_provisioning(agent: AgentInterface, host: OnlineHostInterface, mngr_ctx: MngrContext) -> None:
+    """Install the usage gate marker for pi agents so the lifecycle extension emits usage events.
+
+    Skips non-pi agents. Written to the agent state dir, which the extension
+    reads (``$MNGR_AGENT_STATE_DIR/pi_emit_usage``) once at startup.
+    """
+    if not isinstance(agent, PiCodingAgent):
+        return
+    state_dir = get_agent_state_dir_path(host.host_dir, agent.id)
+    host.write_file(state_dir / _USAGE_GATE_FILENAME, b"1")
+
+
+@hookimpl
+def aggregate_usage_source(
+    source_name: str,
+    agents_events: dict[str, list[UsageEvent]],
+    since_seconds: int,
+    now: int,
+) -> UsageSnapshot | None:
+    """Aggregate the pi usage source; decline every other source.
+
+    pi reports each assistant message's own cost/tokens (not a cumulative total),
+    so this is the session-incremental strategy. Returning None for non-pi sources
+    lets the firstresult hook fall through.
+    """
+    if source_name != _PI_USAGE_SOURCE_NAME:
+        return None
+    return aggregate_session_incremental(source_name, agents_events, since_seconds=since_seconds, now=now)

imbue_mngr_pi_coding_usage-0.1.0.dist-info/METADATA

@@ -0,0 +1,41 @@
+Metadata-Version: 2.4
+Name: imbue-mngr-pi-coding-usage
+Version: 0.1.0
+Summary: pi usage data provider for `mngr usage` (reader + writer gate; the per-message writer lives in mngr_pi_coding's lifecycle extension)
+Requires-Python: >=3.12
+Requires-Dist: imbue-mngr-pi-coding==0.1.13
+Requires-Dist: imbue-mngr-usage==0.1.5
+Requires-Dist: imbue-mngr==0.2.16
+Description-Content-Type: text/markdown
+
+# imbue-mngr-pi-coding-usage
+
+pi data provider for `mngr usage`. pi loads a single explicit extension
+(mngr_pi_coding's lifecycle extension, via `pi -e`), so the per-message usage
+**writer** lives there -- it already holds each assistant message's cost and
+tokens. This package owns the two usage-specific pieces:
+
+- **The reader**: an `aggregate_usage_source` hookimpl claiming the `pi-coding`
+  source, aggregated session-incrementally (pi reports cost per message, summed
+  per session).
+- **The writer gate**: `on_after_provisioning` drops a `pi_emit_usage` marker in
+  each pi agent's state dir. The lifecycle extension only emits usage events when
+  that marker is present -- so the events are written exactly when their reader
+  (this package) is installed.
+
+## What gets captured
+
+pi computes per-message cost client-side (`usage.cost.total`), so cost is
+**REPORTED** (no estimation). Each assistant `message_end` appends one
+`cost_snapshot` to `events/pi-coding/usage/events.jsonl` with the reported cost,
+tokens (`input`/`output`/`cacheRead`/`cacheWrite`), the provider-qualified model
+(`<provider>/<model>`), and the session id (the pi session file's basename).
+`cost_mode` is `API_KEY` (pi bills a real provider key).
+
+## Why the writer is in the harness extension
+
+Unlike Claude (statusline shim) or OpenCode (auto-loaded `plugin/*.ts`), pi loads
+exactly one explicit extension owned by mngr_pi_coding. A standalone writer would
+require a harness change either way, so the writer is folded into the lifecycle
+extension (which already extracts the message usage), and this package stays the
+reader + gate.

imbue_mngr_pi_coding_usage-0.1.0.dist-info/RECORD

@@ -0,0 +1,6 @@
+imbue/mngr_pi_coding_usage/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+imbue/mngr_pi_coding_usage/plugin.py,sha256=OIGa6d98BTMpe144EGMGIBD9Z0ymUqbLP57KHuAJS0k,3076
+imbue_mngr_pi_coding_usage-0.1.0.dist-info/METADATA,sha256=p7eI6wKiGWO6FJzceQdrEJPoXkbdLE4FUZc3ZEZSuWY,2012
+imbue_mngr_pi_coding_usage-0.1.0.dist-info/WHEEL,sha256=mffPy8wBnZQn2VnJUU5jE99KsxaSfiyMHV9Yt0aLVxs,87
+imbue_mngr_pi_coding_usage-0.1.0.dist-info/entry_points.txt,sha256=ED8hJD4M8d07CEJIV-TsJzwGtS_00qf5RGQ2ZFT0Nyc,59
+imbue_mngr_pi_coding_usage-0.1.0.dist-info/RECORD,,

imbue_mngr_pi_coding_usage-0.1.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.30.1
+Root-Is-Purelib: true
+Tag: py3-none-any

imbue_mngr_pi_coding_usage-0.1.0.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[mngr]
+pi_coding_usage = imbue.mngr_pi_coding_usage.plugin