Cryptograss:Moods/usage/todo: Difference between revisions

From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
DrivingThatTrain (talk | contribs)
m Merged, says GitHub: https://github.com/cryptograss/magenta/pull/235
DrivingThatTrain (talk | contribs)
m Merged, says GitHub: https://github.com/cryptograss/magenta/pull/303
 
(15 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<todo>
<todo>
- task: Review magenta#235 (Pi on OpenRouter records the model that ran and what OpenRouter billed)
- task: Review magenta#281 (spend by kind of turn as a shared include on the prompts page; data sections redrawn when stale)
   who: re
   who: re
   kind: review
   kind: review
   link: https://github.com/cryptograss/magenta/pull/235
   link: https://github.com/cryptograss/magenta/pull/281
  note: "Reviewed 29 Oct, block 26,300,708: approved. Two notes for magent (see #usage)."
   done: true
   done: true
- task: Merge magenta#235, then redeploy hunter and maybelle
- task: Merge magenta#281, then redeploy maybelle
   who: justin
   who: justin
   kind: merge
   kind: merge
   link: https://github.com/cryptograss/magenta/pull/235
   link: https://github.com/cryptograss/magenta/pull/281
   done: true
   done: true
- task: Review magenta#237 (usage section on the prompts page)
- task: "Review magenta#303 (Prompts: OpenRouter default in most expensive turns, click Mood to drill down)"
   who: re
   who: re
   kind: review
   kind: review
   link: https://github.com/cryptograss/magenta/pull/237
   link: https://github.com/cryptograss/magenta/pull/303
- task: Merge magenta#237 after #235 (retarget to main), then redeploy maybelle
  done: true
- task: Merge magenta#303, then redeploy maybelle
   who: justin
   who: justin
   kind: merge
   kind: merge
   link: https://github.com/cryptograss/magenta/pull/237
   link: https://github.com/cryptograss/magenta/pull/303
  done: true
- task: "Once #251 has real plan readings, turn headings show OpenRouter turns in billed dollars and Claude Code turns as the 5-hour window after them (\"5h 44% (+2)\"), not list-price dollars"
  who: magent
  kind: code
- task: End-to-end tests of the cost path (Pi event to stored row to page), including routers
- task: End-to-end tests of the cost path (Pi event to stored row to page), including routers
   who: re
   who: re
Line 28: Line 34:
   kind: decision
   kind: decision
   note: Pi session files hold each call's generation id; the record's event ids derive from session and timestamp, so rows can be matched exactly.
   note: Pi session files hold each call's generation id; the record's event ids derive from session and timestamp, so rows can be matched exactly.
- task: Set a daily spend limit on the OpenRouter key (it has none)
  who: justin
  kind: config
  link: https://openrouter.ai/settings/keys
</todo>
</todo>

Latest revision as of 22:09, 8 November 2026

  • ☐
    Once #251 has real plan readings, turn headings show OpenRouter turns in billed dollars and Claude Code turns as the 5-hour window after them ("5h 44% (+2)"), not list-price dollars
    code · magent
  • ☐
    End-to-end tests of the cost path (Pi event to stored row to page), including routers
    code · re
  • ☐
    Daily check of the page's OpenRouter total against OpenRouter's billed total (/api/v1/key usage_daily)
    code · re
  • ☐
    Decide whether to backfill OpenRouter's billed cost onto past routed Pi calls (writes to the record)
    decision · justin
    Pi session files hold each call's generation id; the record's event ids derive from session and timestamp, so rows can be matched exactly.
  • ☐
Done (4)