oh-my-pr 4.6.0 → 4.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -72,13 +72,14 @@ Then:
72
72
  - Pushes verified fixes back to the PR branch
73
73
  - Can automatically create a GitHub release when a merged PR is important enough to justify a version bump
74
74
  - Keeps logs, run history, and PR state on your machine
75
+ - Shows anonymous local usage totals for app opens, tracked PRs, merged PRs, and fixes made
75
76
  - Exposes the same system through a dashboard, local API, and MCP server
76
77
 
77
78
  ## Technical Details
78
79
 
79
80
  ### Local-First
80
81
 
81
- oh-my-pr runs on your machine and works with your local agent CLI. Repository caches (`repos/`), worktrees (`worktrees/`), logs (`log/`), and app state (`state.sqlite`) live under `~/.oh-my-pr` by default. Set `OH_MY_PR_HOME` if you want a different location.
82
+ oh-my-pr runs on your machine and works with your local agent CLI. Repository caches (`repos/`), worktrees (`worktrees/`), logs (`log/`), and app state (`state.sqlite`) live under `~/.oh-my-pr` by default. Set `OH_MY_PR_HOME` if you want a different location. Anonymous usage counters are stored in the same local app state and contain only dates and counts, not repo names, PR URLs, or user identity.
82
83
 
83
84
  ### Isolation
84
85
 
@@ -102,6 +103,7 @@ Watched repositories default to `My PRs only`. You can switch a repo to `My PRs
102
103
  oh-my-pr can be used in a few ways:
103
104
 
104
105
  - web dashboard: `oh-my-pr`
106
+ - usage dashboard: `http://localhost:5001/usage`
105
107
  - server logs page: `http://localhost:5001/logs`
106
108
  - MCP server: `oh-my-pr mcp`
107
109
  - local REST API: see [LOCAL_API.md](LOCAL_API.md)