Files
RedditBot/docs/configuration.md
T
Jamie BruntonandClaude Opus 5 5deac87cf1 feat: let the operator set the daily comment limit per account
The allowance was derived from the adaptive trust level with no way to
change it, which made the dashboard's "1 / 2 today" unexplainable and
left no way to slow an account down or push one along.

`dailyLimit` is null by default, keeping today's adaptive behaviour. A
whole number between 1 and 50 overrides it and is enforced verbatim in
either direction — it can raise an account above what it has earned or
hold it below. The trust level keeps being tracked underneath and is
reported as `adaptiveAllowance`, so the earned figure stays visible next
to the override, and clearing the field hands pacing back to the ladder.

Raising the limit above the earned allowance does remove the adaptive
backoff after a bad comment, so the dashboard says exactly that where the
limit is set. It does not touch the pause on two consecutive removals, a
comment the public cannot see, or a captcha challenge: those are safety
stops rather than rate controls and no limit setting can disable them.

Also correct two things the page was saying badly. The allowance is now
labelled "used in last 24h" with the trust level shown as what it earns,
because it is a rolling window and not a midnight reset. And a
per-community cap above the account allowance now states how much of it
is actually reachable — "1 of 10 today" beside an account limit of 2 read
as far more headroom than existed, since caps distribute the allowance
rather than adding to it.

Verified against a local instance: override above and below the earned
allowance, unrelated saves preserving it, clearing it through the UI,
rejection of 0/51/2.5/non-numeric, and a limit failing to clear a pause.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-11 21:07:25 +01:00

9.8 KiB
Raw Blame History

Configuration

Precedence and lifecycle

Configuration is validated by ConfigSchema in src/config/index.ts.

  1. DATABASE_PATH identifies the database before application settings can be read.
  2. If app_config exists, the application-owned configuration is loaded from SQLite.
  3. Otherwise, config.yaml is loaded once and the validated application-owned subset is seeded into SQLite.
  4. Environment-owned secrets and database location are injected on every start.

After the initial seed, editing config.yaml does not replace an existing app_config row. Use the authenticated settings/API workflow or a deliberate database migration. The config route validates the complete result before saving.

Environment-owned values

Variable Required Purpose
OPENROUTER_API_KEY Yes OpenRouter authentication.
WEB_DASHBOARD_TOKEN When web is enabled Administrator UI/API credential.
DATABASE_PATH No SQLite location; defaults to ./data/reddit-bot.db.
NTFY_AUTH_TOKEN No Bearer token for a protected ntfy topic.
REDDIT_BOT_AGENT_READ_TOKEN No Read-only API/SSE bearer credential.
REDDIT_BOT_AGENT_CONTROL_TOKEN No Read plus versioned control/job bearer credential.
REDDIT_BOT_API_URL MCP only Base URL; defaults to http://127.0.0.1:3000.
REDDIT_BOT_AGENT_TOKEN MCP only Preferred MCP bearer credential override.

Never document real values. .env is ignored and may contain production credentials; do not print or blindly source it.

Application sections

reddit

  • subreddits: at least one item with name, enabled, type, optional weight, tone, optional scripted opener, and conversation policy.
  • pollIntervalMs: legacy/scheduled polling cadence.
  • userAgent: Reddit JSON request identifier.
  • targetGenders: allowed parsed values.
  • filterSellers, sellerKeywords, sellerDomains: seller policy inputs; see also the conversations section, whose off-platform kill is independent of this flag. The defaults treat Telegram references, including t.me and telegram.me links, as seller signals alongside paid-content platforms and payment prompts.
  • prioritizeRecentPosts, recentWindowMinutes: recency/fallback behavior.
  • maxReadyCandidates: hard ceiling for the active candidate target; valid range 1–500. Runtime lowers the actual target to what authenticated running accounts can send within recentWindowMinutes under current rolling-hour and message-spacing limits.
  • physiqueTargeting: optional image-candidate filter with enabled, inclusive minScore, and inclusive maxScore values from 1 to 10. It is disabled by default. When enabled, a model score outside the range or an image without enough visible body evidence to score is rejected before opener generation. Saving the setting also reconciles prepared image candidates in the ready and delivery-retry stages: candidates that no longer qualify are rejected, while retained candidates receive the newly applied range snapshot shown in the funnel. A candidate already leased for sending is not changed mid-send. The setting is hot-read by existing account runtimes; chat sources are unaffected.

Physique targeting is owned only by its dedicated Monitoring controls. It is excluded from the advanced JSON response. Older cached dashboards may still submit a duplicate advanced copy; the server accepts but ignores that copy so it cannot overwrite the dedicated value persisted in app_config.

Subreddit type is image or chat. Conversation policy contains mode, maxAutomatedTurns, and rapportTurnsBeforeMediaAsk; hybrid rapport turns must be lower than the maximum.

conversations

  • offPlatformKill (default true): end a conversation outright when the reply pushes it to another app, to contact details, or to a payment rail. Independent of reddit.filterSellers.
  • killOnSellerKeyword (default true): a configured seller keyword or domain also ends the conversation. Set false to hand those to an operator instead.
  • aiReplyScreening.enabled (default false): second-stage classifier on inbound replies, run only when the deterministic rules pass. Uses openrouter.chatModel and its fallbacks, and fails open.
  • aiReplyScreening.killConfidence (default 0.8) / flagConfidence (default 0.6): thresholds at which a seller/off-platform/scam/bot verdict kills or hands off.

openrouter

Contains image/chat primary and fallback models plus the analysis, message, and chat-opener prompt templates. The API key is environment-only. Model fallback and prompt changes affect cost, behavior, and experiment attribution and need focused tests plus operator-visible metadata.

growthCommentPrompt is the template the account grower uses to write a public comment on someone else's thread. It supports {subreddit}, {title}, {selftext}, and {flair}. The thread is appended separately as fenced untrusted data and the deterministic safety gate runs on the result regardless of prompt wording, so editing this template changes tone, not the safety boundary.

rateLimit

  • minDelayBetweenMessagesMs;
  • maxMessagesPerHour;
  • jitterMs.

These are per account. Reddit JSON request pacing is separately controlled by RedditRequestCoordinator and is process-global.

browser

  • sessionDir: root for persistent account browser profiles.
  • dryRun: when true, candidate preparation may run but remote sends must not.

Treat changing dryRun from true to false as enabling a real side effect.

database

Contains path, but runtime ownership is DATABASE_PATH, not the persisted application config.

media

Controls periodic sync enablement and interval. Media work remains authentication-bound.

pushNotifications

Publishes selected application events to a single ntfy topic so they reach a phone. Holds the enabled flag, server URL, topic, ntfy priority, and a boolean per event (imageReceived, replyReceived, messageFailed, botStopped, rateLimited, sessionExpired, syncFailed). Editable from Settings → Notifications, which writes through PUT /api/push-notifications; POST /api/push-notifications/test sends a fixed test notification. The access token is environment-owned (NTFY_AUTH_TOKEN), is never persisted to the settings record, and is never returned by the API — the response only reports hasAuthToken.

Delivery is best-effort: an unreachable or rejecting ntfy server is logged and never propagated into the path that produced the event.

strategies and chatStrategies

Each has exploration rate, minimum mature samples, response window, and weighted variants. Variants include an ID and prompt override. Image and chat sources use separate sections so their results are not compared as one experiment.

web

Controls enabled state, port, optional tokens after environment injection, and dangerous debug endpoint enablement. Production secrets should never live in YAML.

Account growth

Growth is configured per account through /api/growth, not through config.yaml or app_config, because the community list, allowance, and pause state belong to one Reddit identity. The stores are account_growth_settings and account_growth_subreddits; see docs/database.md.

Operator-settable per account: enabled, the daily comment limit, minimum spacing, jitter, quiet hours, NSFW opt-in, the community list with per-community weight and daily cap, and pause/resume. browser.dryRun also suppresses growth posting.

dailyLimit is null by default, which leaves the allowance to the adaptive trust level the verification sweep maintains (2/3/5/8/12 per day at levels 0-4). Setting a whole number between 1 and 50 overrides that in either direction and is enforced verbatim; the trust level continues to be tracked and reported as adaptiveAllowance so the earned figure stays visible. Raising the limit above the earned allowance removes the adaptive backoff after a bad comment, so the dashboard says so. It does not affect the removal/shadowban/captcha pause, which is a safety stop rather than a rate control and cannot be disabled by any limit.

A per-community dailyCap only distributes the account allowance; caps are not additive and cannot raise the account total.

Runtime-editable subset

The dashboard/API exposes a deliberate subset: rate limits, dry-run, recency and ready-funnel limits, subreddit definitions/conversation behavior, and selected advanced configuration. Shared transport schemas live in packages/api-contracts/src/config.ts; the backend source schema is still the final validator.

When adding a runtime-editable setting, update all of:

  1. ConfigSchema and defaults.
  2. config.yaml seed/example when appropriate.
  3. ConfigStore persistence rules if ownership changes.
  4. Shared request/response schemas.
  5. The config route's merge/write/read-back behavior.
  6. Dashboard model/control.
  7. backend, contract, route, and dashboard tests.
  8. this document.

Validation and change safety

  • Use Zod for every external or persisted shape.
  • Reject unknown transport fields with strict contracts.
  • Validate relationships (not just types), such as the hybrid turn constraint.
  • Do not log the full config because it contains injected secrets in memory.
  • Configuration that affects running account objects may not be fully hot-reloaded; inspect the owning service before claiming immediate effect.
  • A production PUT /api/config should be followed by an authenticated GET read-back. Do not infer persistence from a 2xx alone.
  • A subreddit listing 404 is persisted as disabled so every account runtime stops polling it.

Local safe setup

Install dependencies and run builds/tests without starting the application. If a local backend is explicitly needed, use a dry-run configuration and verify the database path/port before starting. Importing a real session or calling the start control is a separate live-capable action.