Skip to content

Record ReminderBOT as a dotagents-op-run consumer - #46

Merged
quolu merged 1 commit into
mainfrom
op-run-reminderbot-consumer
Nov 15, 2026
Merged

quolu merged 1 commit into
mainfrom
op-run-reminderbot-consumer

Conversation

@quolu

@quolu quolu commented Nov 15, 2026

Copy link
Copy Markdown
Collaborator

ReminderBOT (main-server /home/kite/reminderbot, owner Grave) will read its secrets through the public ~/.local/bin/dotagents-op-run --env-file <refs> -- <command> entry.

  • docs/feature-map/setup.md: under the 1Password table, names the public entry, points to the existing reader row as the canonical contract, and lists ReminderBOT as a known consumer. The behaviors ReminderBOT relies on are already in that row: values passed with trim:false (exact bytes, multiline PEM included); OP_SERVICE_ACCOUNT_TOKEN removed from the child; token taken from env, else the OS store; on a read failure, exit 2 and the child is not started.
  • docs/feature-map/setup.mmd: adds ReminderBOT wrapper -> dotagents-op-run -> child, plus the failure edge.
  • No helper code change. lint-md and tests/docs/current-docs pass locally.

🤖 Generated with Claude Code

The setup contract row for op-secret/dotagents-op-run already covers what ReminderBOT
needs. This names the public entry, records ReminderBOT (main-server, owner Grave) as
a consumer, and draws the connection in setup.mmd. No helper code change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@quolu
quolu merged commit 9bb825b into main Nov 15, 2026
5 checks passed
@quolu
quolu deleted the op-run-reminderbot-consumer branch November 15, 2026 03:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant