Docs menu
Get started
Quickstart Install: Claude Code Install: Codex Install: Kiro Install: other clients API keysConcepts
How a run works The app profile The severity model What a run does not sayTools
check_access claim_trial_key set_profile run_lint get_law resolve_domain_jurisdiction submit_feedback upload_lint_runGuides
A whole run, end to end Console TestPack in CIReference
Endpoint and transport lexlint.yml schema Errors ChangelogHelp
Support and feedbackTools
submit_feedback
Tell the people who build LexLint what went wrong.
What it does
It writes your feedback on LexLint to the people who build it, recorded
against your UnGovr account so we can write back. Arguments:
comments (required), usage_summary, client,
plugin_version.
An agent should call it only when you ask it to, and send only what you have explicitly approved. It should draft the usage summary from what it actually did, show you the exact payload, and send that and nothing else. It should never read your session transcript to build one: if you have pasted a key into a session, it is recorded there. Running it is your decision every time.
Two other things are recorded automatically, and they are the whole of the rest of the
list. Which plugin version you are running, forwarded with the
check_access preflight and stored on its own, in a place that holds nothing
but version numbers. It tells us whether anyone is still on a bundle old enough that
retiring a tool name would break them. A version string and nothing else: not your key,
not your IP address, and no record of what you linted.
A record of each request to the LexLint server. Each one says what the request was (which tool was called, or a step of connecting, such as listing the tools), which coding tool sent it (Claude Code, Codex, Cursor or another, never the model behind it), what kind of credential it carried, if any, and whether it succeeded. It is how we count how often LexLint runs, and from which coding tools.
It also holds the country and region (a US state or a Canadian province, for example) that Cloudflare reports for the connection. That is where the connection came from, which for a VPN or a cloud-hosted agent is a data center. It plays no part in which laws a lint applies; those come only from the jurisdictions you declare.
The record holds no IP address, key or account, and nothing from what you linted: not your declarations, your code or your repository. We keep each record for three months and daily totals after that.
Nothing else about your sessions is collected automatically by LexLint. Your key is an UnGovr Open Data key, and that API keeps a request log of its own, set out at https://www.ungovr.org/open-data/api-keys and holding which collection was asked for and a one-way hash of the key, never which jurisdiction you looked up.
It is deliberately not runnable from the console. A Run button on a page you are poking at would file real feedback against your account as a side effect of exploring, and the whole point of the tool is that you approved the text first.
Parameters
| Name | Type | Required | What it takes |
|---|---|---|---|
comments | string | yes | What the developer wants to say, in their own words. Required: a submission with nothing said is not feedback. |
usage_summary | string | no | Optional. A short summary YOU drafted of how the lint was used this session, which the developer read and approved. If no lint ran, omit it rather than inventing one. |
client | string | no | Optional. The agent this ran in, for example "claude-code". |
plugin_version | string | no | Optional. The LexLint plugin version, from .claude-plugin/plugin.json. |