Cryptograss:Moods/emergence/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
Magent (talk | contribs)
Step 4: rename memory_lane_runner_key to magent_runner_key (#185 ba66c431 reads either); follow-up narrowed (via update-page on MediaWiki MCP Server)
Magent (talk | contribs)
Step 4: the subscription token for re on Pi; keep memory_lane_runner_key until step 5 (via update-page on MediaWiki MCP Server)
Line 32: Line 32:
   note: "Runs migration 0025_harness_models. Before step 5, so the endpoint re's poller reports its models to exists when it first starts. magent's own poller is untouched until a hunter deploy, and on Claude Code it reports nothing."
   note: "Runs migration 0025_harness_models. Before step 5, so the endpoint re's poller reports its models to exists when it first starts. magent's own poller is untouched until a hunter deploy, and on Claude Code it reports nothing."
   done: true
   done: true
- task: "Step 4: in the vault: rename memory_lane_runner_key to magent_runner_key (same value); add re_runner_key (any random string), re_pickipedia_bot_password (account Re, login Re@re), re_model (its default, e.g. openrouter/moonshotai/kimi-k3), and model_<vendor>_api_key for each vendor you get a key for"
- task: "Step 4: in the vault: magent_runner_key (done, keep memory_lane_runner_key too until step 5 is deployed), re_runner_key and re_pickipedia_bot_password (done), claude_code_oauth_token (run `claude setup-token` on your laptop), re_model: anthropic/claude-sonnet-5-5; later, model_<vendor>_api_key for any other vendor"
   who: justin
   who: justin
   kind: decision
   kind: decision
   link: "https://github.com/cryptograss/maybelle-config/pull/185"
   link: "https://github.com/cryptograss/maybelle-config/pull/185"
   note: "#185 (ba66c431) reads magent_runner_key and falls back to memory_lane_runner_key, so the rename is safe in either order; keep the value exactly as it is. The vendor keys are shared by every agent (re now, orang and blu later); re_<vendor>_api_key would give re its own, only if it ever needs a separate limit or bill. Vendors: openrouter (https://openrouter.ai/settings/keys — one key, 401 models), anthropic (https://console.anthropic.com/settings/keys), openai (https://platform.openai.com/api-keys), google (https://aistudio.google.com/apikey), moonshotai (https://platform.moonshot.ai/console/api-keys), deepseek (https://platform.deepseek.com/api_keys). Any you skip show greyed in the menu."
   note: "re stays on Pi. The setup-token token reaches it as ANTHROPIC_OAUTH_TOKEN (Pi, Anthropic's models on the subscription) and CLAUDE_CODE_OAUTH_TOKEN (if an agent is ever on Claude Code); shared by every agent. Other vendors' keys, also shared: openrouter (https://openrouter.ai/settings/keys — one key, 401 models), openai (https://platform.openai.com/api-keys), google (https://aistudio.google.com/apikey), moonshotai (https://platform.moonshot.ai/console/api-keys), deepseek (https://platform.deepseek.com/api_keys). Any vendor without a key shows greyed in the menu."
- task: "Step 5: merge maybelle-config#185 (Mood containers; re's home docs-tests-qa), deploy maybelle, then hunter with --rebuild; ping magent, then @re in docs-tests-qa"
- task: "Step 5: merge maybelle-config#185 (Mood containers; re's home docs-tests-qa), deploy maybelle, then hunter with --rebuild; ping magent, then @re in docs-tests-qa"
   who: justin
   who: justin
   kind: deploy
   kind: deploy
   link: "https://github.com/cryptograss/maybelle-config/pull/185"
   link: "https://github.com/cryptograss/maybelle-config/pull/185"
   note: "Maybelle first, so memory-lane accepts re's runner key before re's poller starts and reports with it. Agent setup dry-run in a throwaway container, 2026-10-14; the vendor keys (f748058f) checked 10-15: agent.env mode 600, only vendors with a key, values shell-quoted; the shared-or-own lookup and the runner key's old-or-new name checked in ansible-core."
   note: "Maybelle first, so memory-lane accepts re's runner key before re's poller starts and reports with it. Agent setup dry-run in a throwaway container, 2026-10-14; checked 10-15: agent.env mode 600, only keys present, shell-quoted; shared-or-own lookups and the runner key's old-or-new name in ansible-core; Claude Code's config under the agent's home (claude mcp list connects to both servers); Pi takes the setup-token token for Anthropic (964f7286)."
- task: "After re is up: MOOD_RUNNER_KEYS built in one loop over the agents (<agent>_runner_key), not one {% if %} each; drop the memory_lane_runner_key fallback once the vault has only the new name"
- task: "After re is up: MOOD_RUNNER_KEYS built in one loop over the agents (<agent>_runner_key), not one {% if %} each; drop the memory_lane_runner_key fallback once the vault has only the new name"
   who: magent
   who: magent

Revision as of 15:37, 15 October 2026

What people in the magent-self Mood have been left to do. Kept by magent; anyone may tick an item.

Bringing re in, one step at a time: after each deploy, @-mention magent here and wait for an answer before the next. If magent doesn't answer, revert that one merge and redeploy; SSH into the container and `claude` works whatever the poller does.

Done (14)