PolitiClaw Plugin

A local-first OpenClaw plugin that turns your agent into a civic copilot that holds your representatives accountable to the values you declare. It learns the stances you care about, watches federal legislation and elections on your behalf, flags when your reps' votes and actions align — or don't — with those stances, and drafts letters you send yourself. All on your own machine; no send path, no prescriptive voting recommendations, no stance it invented for you.

Political data stays in a plugin-private SQLite database under the gateway's state directory. It does not write to shared agent memory.

Install

Install the plugin into a running OpenClaw gateway:

openclaw plugins install @politiclaw/politiclaw

Reload the gateway (or restart the OpenClaw app) to pick up the new tools.

Working on the plugin from a local checkout instead? See Development.

First-run checklist — 10 minutes to your first alert

Use slash commands for quick checks and ask your agent to call tools for setup. politiclaw_configure is an agent tool, not a shell command, so it is invoked through the agent rather than typed into a terminal.

Find the next setup step. Run /politiclaw-setup. It returns a copyable prompt for the agent, starting with “Call the agent tool politiclaw_configure with my street address…”.
Declare the stances you want to measure your reps against. Use the issueStances input on politiclaw_configure during setup, or add/edit one later with politiclaw_issue_stances (action set, list, or delete). Each stance can also carry a short note for the specific concern inside the issue bucket and sourceText for your original phrasing; letters, call scripts, rep reports, and the monitoring contract use that nuance. These stances are the baseline PolitiClaw uses for every accountability score — no score exists without them.
Continue setup whenever something changes. Ask your agent to call politiclaw_configure to refresh reps, change monitoring cadence, save keys, or update the saved address.
Wait for the first alert. The weekly summary cron fires once a week; election-proximity alerts fire more often as an election in your state approaches. If you want a preview of what the next weekly digest will pull from, call politiclaw_check_upcoming_votes with a 7-day window — that is the main input the weekly summary composes from. There is no "run the weekly summary now" tool; the digest is cron-driven and assembled via the politiclaw-summary skill.

If anything in this path looks wrong, run /politiclaw-status, /politiclaw-doctor, or /politiclaw-version — see Troubleshooting.

API keys

The fastest path: paste the key into chat. Ask your agent to call politiclaw_configure. When the api.data.gov key is missing, the agent walks you through signup and asks you to paste the key (and any optional upgrade keys you have) back into chat. The plugin writes them through the OpenClaw gateway's config.patch method (validated, audited, optimistic concurrency). The gateway then restarts itself once to pick up the new values — reconnect after the restart, run /politiclaw-setup, and continue from the saved checkpoint.

politiclaw_configure also handles one-off updates after onboarding: passing apiDataGov (or any optionalApiKeys) saves them straight to plugins.entries.politiclaw.config.apiKeys.* without re-running the full setup flow.

You can still edit ~/.openclaw/openclaw.json by hand under plugins.entries.politiclaw.config.apiKeys.* if you prefer; both paths land in the same file.

One named key is required; the other named keys are optional upgrades.

The plugin's config schema declares three wired keys — apiDataGov, geocodio, and googleCivic. The runtime reads only those keys. Unknown legacy key strings may still validate so older configs keep loading, but politiclaw_configure and politiclaw_set_api_keys will not save roadmap keys and no current adapter reads them. The roadmap rows below signal where the plugin is headed (state coverage) without declaring those providers as supported.

Key	Status	Required?	What it unlocks
`apiDataGov`	Active	Required	Federal bills, House roll-call votes with member positions, committee schedules, and FEC campaign-finance data. One `api.data.gov` key covers both `api.congress.gov` and OpenFEC. Senate roll-call votes ingest separately through voteview.com (zero-key, no signup). Free, instant signup at api.data.gov/signup.
`geocodio`	Active	Optional	Reps-by-address via API. Without it, the plugin uses a zero-key local shapefile pipeline — Geocodio trades disk footprint for API simplicity.
`googleCivic`	Active	Optional but required for `politiclaw_get_my_ballot`	Google Cloud API key with the Civic Information API enabled. Distinct from `api.data.gov`.
`openStates`	Roadmap	—	Planned: state bills and votes with individual member positions. Until wired, state bill lookup is narrative-only via LLM search; state vote positions and state change-detection are not available.
`legiscan`	Roadmap	—	Planned: alternate state bills source. Free tier covers 30,000 queries/month and would substitute for `openStates`.
`followTheMoney`	Roadmap	—	Planned: state-level campaign finance. State finance is not covered until this is wired.

To validate that your active keys are wired up correctly, run /politiclaw-doctor — it checks every key the plugin actually accepts and reports which tools each missing key gates.

Override recipes

Agent behavior for PolitiClaw is driven by plain-markdown skills under skills/. You can edit these in place to retune the plugin's voice, guardrails, or ordering without rebuilding the plugin — the gateway re-reads them on reload.

Current skills:

politiclaw-onboarding — first-run flow that helps politiclaw_configure collect issue stances in a conversational or quiz-style handoff.
politiclaw-monitoring — how the agent interprets change-detection results, alignment scores, and election-proximity alerts.
politiclaw-ballot — how the agent explains ballot items without prescribing a vote.
politiclaw-outreach — how the agent drafts letters (user-authored, never auto-sent).
politiclaw-summary — format and scope of the weekly digest.

Typical edits: tightening or relaxing the anti-prescription guardrails, adding project-specific stance vocabulary, or changing the default tone of drafted letters. Changes to skills do not require npm run build.

Dashboard

The plugin registers a local-only dashboard at /politiclaw on the gateway's HTTP surface. It shows your preferences, reps and alignment scores, installed monitoring jobs, upcoming election, recent alerts, recent drafted letters, and recent bill-linked roll-call votes — all driven by the plugin's private SQLite DB.

The dashboard is also editable:

Preferences form — save address, ZIP, state, district, or monitoring cadence without going through the agent.
Pause all / Resume all — bulk-toggle every PolitiClaw cron job on the gateway.
Quick-vote buttons — record agree/disagree/skip signals on recent bill-linked votes. Each click is stored as a stance signal that nudges your rep alignment scores.
Request re-draft — flag a past letter for re-drafting. The next agent session picks up the flag and drafts a fresh version; the browser does not invoke tools directly.

Because the dashboard is registered with auth: "plugin", the gateway adds no auth layer. POST requests are protected by a double-submit CSRF token (pc_csrf cookie paired with an X-PolitiClaw-CSRF header) and bodies are bounded to 256 KB. Exposure is intended to be local-only; operators who expose the gateway off-host must front the dashboard themselves.

Troubleshooting

Run /politiclaw-doctor first. It checks, in one pass:

Schema migrations are up to date.
The SQLite database passes integrity checks.
Preferences are populated (address, zip, state).
Every recognized API key is classified as required / optional / missing, with the gated tools listed.
The reps cache has been populated and isn't stale.
Every monitoring cron job the plugin expects to own is installed.

Each check returns ok, warn, or fail with an actionable hint for every non-ok result. The tool is read-only — it never mutates state.

Cross-machine caveat: the doctor runs inside the OpenClaw gateway process. If your gateway runs on a different host than where you installed the plugin source, gateway-side errors (missing cron adapter, unreadable state directory) will surface as fail in the report and have to be fixed on the gateway host.

Plugin installed but tool unavailable

If the package installed but your agent cannot call politiclaw_configure, restart the OpenClaw gateway, verify PolitiClaw is enabled in the plugin registry, then run /politiclaw-version. If /politiclaw-version works but the tool is still unavailable, run /politiclaw-doctor for a storage/package diagnostic.

Gateway restarted during key save

Key saves intentionally restart the gateway. Reconnect to OpenClaw, run /politiclaw-setup, and ask the agent to continue with the prompt it prints. Setup resumes from saved plugin state; you do not need to repeat earlier answers.

Development

Install from a local checkout

From the workspace root:

openclaw plugins install ./packages/politiclaw-plugin --link

The --link install reads from the source path, so edits land without reinstalling.

Build and test

From this package directory:

npm run build
npm run typecheck
npm run test

From the workspace root:

npm run dev:plugin

License

PolitiClaw is released under the MIT License.

PolitiClaw