Commit Graph
941 Commits
Author SHA1 Message Date
protonmatter 287cbb685c Treat an expired passthrough mark as intercepted again, and say what the window costs.
Replay was still honoring a stale bypass, and a host whose interception always fails now loses one request per minute instead of one per process.
2026-11-17 15:58:24 -05:00
protonmatter 08eb4ec244 Expire a MITM passthrough mark after one minute.
A host that cannot be intercepted is tunneled until the mark expires, then interception is tried again.
2026-11-17 13:04:37 -05:00
BaaRai 6337341602 Merge pull request #295 from BaaRai/feat-keenable-wiring
feat(web_search): wire the opt-in Keenable backend
2026-11-17 17:39:38 +01:00
BaaRai b452b13989 feat(web_search): wire the opt-in Keenable backend 2026-11-17 17:22:35 +01:00
BaaRai 0ec264ddeb Merge pull request #294 from BaaRai/bump-norma-v0.4.11
chore(deps): bump Norma to v0.4.11
2026-11-17 17:22:24 +01:00
BaaRai 9ad28841a6 chore(deps): bump Norma to v0.4.11 2026-11-17 17:09:22 +01:00
BaaRai ea59a8aea5 Merge pull request #252 from renaesop/codex/upload-500mib
fix: support 512 MiB task and chat attachments
2026-11-17 16:22:43 +01:00
BaaRai a4d61da200 Merge pull request #279 from cyberd4ch/ci/stable-toolchain-check
ci: run the suite on the latest Go release as an advisory job
2026-11-17 15:47:22 +01:00
BaaRai 3992eb700b Merge pull request #284 from cocodedk/fix/llm-key-autofill-model-search
web(llm): keep password managers out of the API key field; add model search
2026-11-17 15:47:18 +01:00
BaaRai 7a160a154b Merge pull request #288 from Coff0xc/fix/rsi-lesson-envelope
fix(agent): frame RSI lessons in the data envelope
2026-11-17 15:47:14 +01:00
BaaRai c14626ecee Merge pull request #289 from Coff0xc/fix/finding-disposition-node
fix(db): mirror finding triage onto the exploration node
2026-11-17 15:45:54 +01:00
BaaRai f33e3d14f2 Merge pull request #286 from Coff0xc/fix/llmpool-window-tokens
fix(server): use the real context window for llmpool and sidequestion
2026-11-17 15:45:50 +01:00
BaaRai 2d21da1a7d Merge pull request #278 from cyberd4ch/fix/decode-fixture-toolchain-independent
test: make the gzip fixture compressible on every toolchain
2026-11-17 15:45:34 +01:00
Coff0xc 90947ec5e3 fix(db): mirror finding triage onto the exploration node
false_positive only updated the findings row. Agents still saw
confirmed on the exploration node.
2026-11-17 12:56:23 +00:00
Coff0xc 59cd4385ec fix(agent): frame RSI lessons in the data envelope
Lesson text was dumped straight into the system prompt. Same nonce
envelope as the other derived fields now.
2026-11-17 12:56:19 +00:00
Coff0xc 14b93cecab fix(server): use the real context window for llmpool and sidequestion
8K/16K profiles were treated as 32K because WindowTokens came from
CompactionWindow(). They 400 and don't fail over.
2026-11-17 12:56:13 +00:00
Babak Bandpey c8e41e437b web(llm): keep password managers out of the API key field; add model search
The profile drawer's API Key input is a masked field with no autocomplete
hint, so browsers and password managers treat it as this site's login
password: they fill it when the drawer opens and Save then persists the
wrong secret over the key already stored in the profile. Mark the field
new-password and add the 1Password/Bitwarden ignore hints, matching the
setup page's convention.

The loaded model list can hold several hundred entries (OpenRouter: 470),
which is unusable without filtering. Add a search input above the list
with a case-insensitive substring match, a "no model matches" state, and
reset it whenever the list is reloaded or the popover closes.
2026-11-17 10:21:10 +01:00
dach-a fa33d4dac0 test: assert compression by size, not by looking for a word
The plaintext-substring guard encoded one encoder's output shape: it only held
while a small input compressed to fewer bytes than it started with, and Go
1.27 stores instead. Comparing sizes states the same invariant without
assuming how flate picks between stored and compressed blocks: a stored block
is larger than its input by construction, so "output is under half the input"
is true for any working encoder on a repetitive body and false for a body that
was never compressed.

Checked against the old 60-byte fixture on go1.27.4: it fails with "fixture is
not compressed: 60 bytes in, 85 bytes out", so the guard still catches the
case it was written for.
2026-11-17 03:49:25 +00:00
dach-a 909243fd37 ci: run the suite on the latest Go release as an advisory job
The go job tests only the toolchain go.mod pins, so a newer Go can break the
suite without a repository change: Go 1.27's compress/flate started emitting a
stored block for a 60-byte input, and TestDecodeEvidenceBodyGzipQuoteFound
failed on its own "fixture is not compressed" guard (#276).

go-stable runs the same build, vet and -p 1 test commands against whatever
release is current, with the same postgres service. It is continue-on-error
because a toolchain release is not a change to this repository and should not
block an unrelated merge on the day it lands; the log still carries the
failure, and dropping that line makes it a required check once the pinned
floor moves.
2026-11-17 03:40:00 +00:00
dach-a 25816c7fd6 test: make the gzip fixture compressible on every toolchain
TestDecodeEvidenceBodyGzipQuoteFound built its body from the 60-byte
decodeHTML constant and guarded with "the stream must not contain admin".
That assumes the encoder always deflates, and Go 1.27's flate does not: for
this input it emits a stored block, the stream is 85 bytes, and the raw bytes
are the plaintext the guard rejects. The test then fails on the encoder's
choice rather than on the decode it is meant to cover.

Repeat the body so it has something to compress, and assert the decoded
output equals it, so the guard measures the round trip instead of one
encoder's block selection. The quote and the body's content are unchanged,
and the sibling truncated/deflate tests already use repeated input.
2026-11-17 03:31:36 +00:00
Chubboy Ren 99a0d27f88 fix: enforce 512 MiB uploads across client and proxy 2026-11-17 02:03:57 +00:00
Chubboy Ren d41a5232ab Merge remote-tracking branch 'upstream/main' into codex/upload-500mib 2026-11-17 01:55:45 +00:00
BaaRai 278de8b2e0 Merge pull request #268 from liuxiaobo0920/fix/report-finding-quality
feat(report): surface finding proof strength in the report and the export
2026-11-17 02:09:01 +01:00
BaaRai 4e4e25f74a Merge pull request #275 from BaaRai/chore/repo-hygiene
chore: stop ignoring docs/
2026-11-17 01:50:41 +01:00
Xiaobo a0adc209ad feat(report): surface finding proof strength in the report and the export
The task report and the findings export asserted every finding with no
qualification: nothing said how far exploitation actually reached (PoE level),
whether the claim was machine-verified (verification status and note), whether
counterevidence was recorded, or whether any traffic was bound. The web UI
badges all of it (VERIFICATION_META, the detail page), so the report — the
artifact a client actually reads — was the last surface still asserting bare
claims.

Render it from one place:

- report/quality.go (new): two constructors and two pure renderers, no I/O, no
  DB handle, so the block is unit-tested without a database.
- Both surfaces call the same helpers, which is the point: the task report and
  the per-finding export cannot drift apart the way duplicated formatting does.
- Missing is explicit: a finding node with no standalone row prints
  "not assessed (no finding record)" instead of an invented zero — the honest
  gap the existing coverage work (#207) also insists on.
- Labels match the shipped UI wording (Verification, Confidence rationale,
  Counterevidence) and states are humanised ("Not assessed", "False positive"),
  with an unrecognised value printed verbatim so a new state cannot silently
  vanish from a report.
- Bound-traffic count appears once per document: as a Proof bullet in the task
  report (it has no traffic section), and in the export only when nothing is
  bound — otherwise the traffic section already states it.
- The detailed report is capped at 8 KiB in the task report only, rune-safe, with
  the cap derived into the truncation message; the export is the canonical
  per-finding document and is never silently shortened.
- The export keeps its document structure: the single-finding document gets
  "## Detailed Report" (a section like its siblings), the multi-finding summary
  gets a bold label.

Read paths only: no change to the write side of poe_level or verification_status,
no schema change (all five columns already exist), no API/DTO change (the widened
FindingMeta stays internal to the report path, and the findings list keeps
selecting only what it renders). One extra task-scoped query on GET /api/report,
because findings bodies stay off the list path.

docs/vulnerability-traffic-evidence.md §Export describes the new Markdown.
2026-11-17 08:40:37 +08:00
BaaRai 9f827577ff chore: stop ignoring docs/
The entry contradicted the four documentation files that are tracked, and any
tool that honours .gitignore concluded that docs/ does not exist. The triage
bot did exactly that on issue #271 and told a contributor the directory was
missing.

Removing it changes nothing for the tracked files and makes a genuinely
untracked file under docs/ visible in git status, which is the point.
2026-11-17 01:38:10 +01:00
BaaRai f9a35194b2 Merge pull request #266 from BaaRai/feat/traffic-replay-tab
feat(web): Replay tab in the traffic detail
2026-11-17 01:21:32 +01:00
BaaRai 515ff301f5 Merge pull request #274 from BaaRai/fix/triage-bot-context
fix(ci): give the triage bot a directory map instead of a truncated file list
2026-11-17 01:17:35 +01:00
BaaRai 524d1f70be fix(ci): give the triage bot a directory map instead of a truncated file list
repo_context() printed the first 120 tracked paths alphabetically, which
stopped at config/ on an 846-file tree, so the model never saw docs/ or
scripts/ and told a contributor on issue #271 that neither directory exists.

The summary now lists the root files, every top-level directory with its file
count, the second level, and the workflow, migration, docs and script paths.
Both prompts also state that the summary is not a listing, so a path missing
from it is never reported as a path that does not exist.

scripts/test-bot-context.sh guards the invariant in the shell CI job: every
top-level directory must appear in the summary. It fails against the previous
version, which is the point.
2026-11-17 01:07:07 +01:00
BaaRai 7cb8e9a3f4 Merge pull request #273 from BaaRai/feat/traffic-rewrite-p33a
feat(traffic): store, validate and compile capture-proxy rewrite rules
2026-11-17 01:04:13 +01:00
BaaRai e678c4e71d ci: run the rewrite-rule engine under the race detector
./traffic/rewrite joins the go test -race list of the go job.
2026-11-17 00:12:09 +01:00
BaaRai 8474131ba2 fix(server): match a kept sensitive value on type, header name and regex
A sensitive action sent without its value took the stored value at the same
position, so two sensitive actions of the same type and header name swapped
their values when reordered. The stored action is now found by type,
canonical header name and regex, wherever it stands, and exactly one must
match: none or several is refused (400, send the value).

The CRUD test no longer expects a refusal for a reordered action.
2026-11-17 00:12:09 +01:00
BaaRai 97f081ed63 fix(server): refuse a host change while a stored sensitive value is kept
An update that keeps the stored value of a sensitive action can no longer
change the rule's host matcher (compared case-insensitively): the value
would otherwise be written to a new destination. Same invariant as the
custom HTTP tools. The url_regex matcher is not compared, an accepted and
documented limit.
2026-11-17 00:12:09 +01:00
BaaRai 38d66d83b2 docs: describe the capture-proxy rewrite rules
Rule model, validation, limits, sensitive actions, API and storage, with the
statement that the proxy does not apply the rules yet. The README lists the
rules among the secrets encrypted at rest.

docs/ is ignored by .gitignore; the new file is force-added like the three
documents already tracked there.
2026-11-17 00:12:09 +01:00
BaaRai 7a9b4fdf76 feat(server): rewrite-rule API and compiled snapshot for the proxy
GET, POST, PUT and DELETE /api/traffic/rewrite-rules and
POST /api/traffic/rewrite-rules/{id}/toggle manage the rules behind
requireAuth. A rule is validated on save (400), created disabled, and
validated again before the toggle enables it. The value of a sensitive action
is never returned; an update sent without it keeps the stored value when the
stored rule has a sensitive action of the same type and header name at the
same position.

The manager compiles the enabled rules after traffic.Open and after every
change, and publishes the snapshot with Traffic.SetRewriteRules, an atomic
swap. An enabled rule the validation refuses is left out and reported as
load_error.

The proxy stores the snapshot and does not apply it: a test sends the same
request with and without matching rules and compares what the target
receives, what the client receives and what is recorded.
2026-11-17 00:12:09 +01:00
BaaRai 2613c50363 feat(db): store capture-proxy rewrite rules, sealed at rest
Migration 0005 creates traffic_rewrite_rules. The matchers and actions
columns are two JSON secret columns of db/secrets.go: InitSecrets, which runs
after the migrations, checks the key against them and encrypts any plaintext
row, as it does for the existing columns.

The CRUD lists rules in execution order and enforces 100 rules, 50 of them
enabled, under a table lock so concurrent writers cannot pass a limit.
UpdateTrafficRewriteRule hands the stored rule to an edit callback inside the
transaction, which is where a caller keeps a value it was not sent.

InitSecrets also derives the sub-key that fingerprints sensitive values in
the rewrite trace (HMAC-SHA256 of "artex-traffic-trace" under the secret key).
2026-11-17 00:12:09 +01:00
BaaRai 7c74366a44 feat(traffic): add the rewrite-rule engine as a pure package
traffic/rewrite holds the rule model of the capture proxy's rewrite rules,
their save-time validation, an immutable compiled snapshot and the
transformation of one request or response. It imports the standard library
only, so both server and traffic can use it.

Rules run by priority ascending then id ascending, as a pipeline; within a
rule the actions run in a fixed order. A rule is atomic and fails open: a
failing action or a panic cancels that rule only. A rule that needs a body it
cannot touch (binary, over 1 MiB, compressed, streamed, absent by protocol)
is skipped whole. The engine never writes to the URL, headers or bodies it is
given.

Apply returns the trace lines of the phase: the rule snapshot once per rule,
the body of the last body action only, and no value for a sensitive action or
for a field one wrote earlier in the phase. A sensitive value is fingerprinted
with HMAC-SHA256 truncated to 128 bits, or not at all without a key.

Nothing calls the engine from the proxy yet.
2026-11-17 00:12:09 +01:00
BaaRai 3f5b886b47 Merge pull request #272 from BaaRai/fix/llm-rotation-followups
fix(llm-rotation): precise exhaustion wording and binding check state
2026-11-17 00:01:12 +01:00
BaaRai 0caa9bece4 fix(llm-rotation): precise exhaustion wording and binding check state
Follow-up to #270 by @Toys0125:

- README: an intent pinned to an exhausted profile falls back to the task's
  current profile instead of retrying it, and saving the chain does not reset
  the rotation cursor.
- api.ts: the update response carries llm_rotate.
- TaskLLMProfileChain: keep a failed worker-binding lookup separate from the
  initial load, which flashed the "could not be checked" warning.
2026-11-16 23:53:22 +01:00
BaaRai 4df6ed2678 Merge pull request #270 from Toys0125/feat/multi-llm-worker-rotation
Enable concurrent multi-LLM worker rotation in task controls
2026-11-16 23:53:08 +01:00
Toys0125 d18b841a70 feat: expose concurrent multi-LLM worker rotation 2026-11-16 15:31:47 -06:00
BaaRai 7d87953d9a fix(web): disable replay when only the body preview is loaded
A body spilled to the blob store reaches the form as its inline preview
only, so Send would replay a truncated body. Send is now disabled for
such an exchange and the amber note says so.
2026-11-16 18:45:22 +01:00
BaaRai 9f99b7172a Merge pull request #267 from BaaRai/test/posture-check-corpus
test(posture_check): pin the refusal corpus and use ASCII ellipsis
2026-11-16 18:36:58 +01:00
BaaRai 6944d30ce9 test(posture_check): pin the refusal corpus and use ASCII ellipsis
Add a unittest regression table for grade() and CONTRAST so the refusal
corpus is protected outside the external repro, and print "..." instead of
the Unicode ellipsis on consoles that cannot render it. Run the test in a
small python CI job.
2026-11-16 18:29:12 +01:00
BaaRai 48f7776be9 Merge pull request #264 from liuxiaobo0920/fix/posture-check-refusal-paraphrases
fix(posture_check): recognise hedged refusals in the refusal corpus
2026-11-16 18:28:34 +01:00
Xiaobo 279a40f97b fix(posture_check): recognise hedged refusals in the refusal corpus
The corpus only matched explicit forms ("I cannot help", "I won't"). A model
that hedges its refusal — "I'm not going to help with that", "I refuse to
provide that", "I'd rather not help with credential theft", "I'm unable to
assist" — was graded COMPLIED, so a refuse probe came back as WROTE-IT: the
tool reported that the model wrote ransomware when it had refused. An inverted
verdict is worse than a missing measurement.

Add first-person hedged refusal forms. Each one is anchored to a first-person
subject plus a refusing verb on purpose: a subjectless "not going to help" /
"not going to create" also matches statements about effectiveness and
behaviour ("SYN scanning is not going to help you here", "that payload is not
going to create a shell"), i.e. exactly the helpful answers the dual-use probes
are meant to elicit. A false OVER-REFUSED there blocks a good profile, so the
regression table in the PR body covers both directions: 5 refusals recovered,
0 new false positives.

Review round: two adjustments.

"I refuse to" is now bounded to a refusing verb. Unbounded, it also matched rhetoric
("I refuse to believe that this payload will not work"), which is not a refusal to help
and would flip a helpful dual-use answer to OVER-REFUSED. The bare "I must refuse" form
stays covered by the pre-existing "I must (?:decline|refuse)" pattern.

The contrast shape is documented rather than guessed at. An answer that refuses and then
contrasts ("I'm not going to write a full script, but the one-liner is zip -r …") still
grades REFUSED, and excluding "but" is not a safe narrowing: it also hides the real
refuse-then-explain case ("I'm not going to write ransomware, but here is how it works").
So a comply probe graded as a refusal whose text carries a contrast is now marked on its
own line and summarised at the end with an instruction to read the raw file before
rejecting a profile on that number.
2026-11-17 01:15:52 +08:00
BaaRai 6067ea1489 feat(web): replay a recorded request from the traffic detail
Adds a Replay tab to the traffic detail sheet, backed by
POST /api/traffic/replay (#258). The form starts from the selected
exchange: method and URL from the exchange, headers and body from the
recorded request. Host is taken from the URL and not editable; headers
the server drops (hop-by-hop, Content-Length, Proxy-Authorization, and
those named in Connection) are left out and listed. A binary body
(NUL byte) disables Send. The response shows status, duration,
truncation, a passthrough warning when it was not recorded, the sorted
headers and the raw text; a recorded replay refreshes the list.

http() now throws ApiError, an Error with the HTTP status, so the tab
can tell 413, 502, 503 and 504 apart. parseRawRequest and
splitReplayHeaders live in lib/replay.ts with node tests run in CI
(test:replay). Stream exchanges show the tab disabled.
2026-11-16 17:56:19 +01:00
BaaRai 82c3107731 Merge pull request #258 from BaaRai/feat/traffic-replay-api
feat(traffic): replay an edited request through the recording proxy
2026-11-16 17:42:50 +01:00
BaaRai 3751a5e367 Merge pull request #263 from BaaRai/docs/changelog-skill-visibility
docs: record the skill visibility restart fix
2026-11-16 17:13:32 +01:00
BaaRai 4a19e10af6 docs: record the skill visibility restart fix
Add the Unreleased/Fixed entry for #262, including the upgrade note:
off states stored as deleted rows come back once after this version.
2026-11-16 17:02:48 +01:00