AI Support Agent v6.0.3

Release Date: August 24, 2026 Tags: KNOWLEDGE, RETRIEVAL, ROUTING, P2P

Overview

The agent could not send a P2P trader to their own profile, because it did not know the page existed.

"Where do I see my rating?" and "why is nobody taking my offers?" are questions about the page a counterparty reads before deciding whether to deal with somebody — their completion record, how fast they release escrow, and the reviews people have left them. The agent answered both by pointing at the trades list, which carries a private trade history and cannot show a review.

The agent never types a URL: it proposes an action, and the route is re-checked against a catalogue of pages the platform actually has. A page missing from that catalogue is a place the agent cannot send anyone, however clearly a customer asks. This release adds the one that was missing.

It also repairs something the agent reads from rather than links to. The knowledge index was storing documentation markup instead of documentation — screenshot coordinates, layout attributes and stray punctuation, indexed as though they were words a customer might search for. Press Reindex on the knowledge page after updating.

Update Instructions

pnpm updator

Restart the backend, then press Reindex on Admin → AI Support → Knowledge so the index is rebuilt with the corrected text. Nothing is lost if you skip it; retrieval simply stays as it was.

There is no database change. The route this adds exists in P2P Trading v6.3.2 — installing this release against an older P2P is harmless, but the page will not be there to reach.

Fixed

The knowledge index was full of markup, not documentation

The documentation is written in a directive dialect — a callout is :::warning{title=…}, an API reference line is ::endpoint[…]{method=… path=…}, a numbered marker on a screenshot is ::pin{n=1 x=11.4 y=17.2}. Nothing between the raw markdown and the search index had ever turned those into the text a reader actually sees on the page, so the syntax itself was indexed. A walkthrough step reached the index looking like this:

::pin{n=1 x=11.4 y=17.2} **Choose Buy** — the toggle above the board…

pin, x, 11 and 4 are then terms the search scores against every customer question, and that chunk is also what the model is shown when it cites a source. Measured on the corpus: 2,525 of 5,887 chunks carried a directive opener, 3,131 carried a stray closer, 683 an endpoint directive and 300 a setting directive.

A chunk now contains what a reader sees. An ::endpoint is indexed as its method, its path, its permission and its sentence — the path being the single most-searched thing on a reference page. A ::pin is indexed as nothing at all, because on the page it is a numbered badge on a picture. Anything that is presentation — an image path, a column count, a percentage offset — is dropped rather than passed through.

• Fixed documentation directives being indexed as raw syntax. Answers now retrieve on the words the page shows.
• Fixed two parsing traps found while doing it: 637 endpoint paths in the corpus contain a brace of their own (/api/p2p/trade/{id}) and used to cut the parse short, leaving stray characters in the prose; and an IPv6-mapped address written in the docs (::ffff:127.0.0.1) parsed as a directive and vanished from the page entirely.

Added

The P2P trader profile is a place the agent can send somebody

• Added /p2p/profile to the route catalogue, described as the customer's own trader profile exactly as other traders see it. It is deliberately a separate entry from /p2p/trades: that one carries their own dealing as private statistics, and this one is the page strangers judge them on.