How AIClaw 3.7.6 Keeps Web Search Sources Available Beyond the Tool Log
A web-search tool can return useful pages while the final answer leaves the reader with no convenient way to inspect them. Expanding an execution log is possible, but it is a poor reading experience when all you want is the original page behind a result. AIClaw 3.7.6 , released on October 10, adds a turn-level source list to its desktop chat. This is a shipped feature in that release, rather than…
AIClaw 3.7.6, released on October 10, introduces a new feature that expands the execution log of a web-search tool to provide a more convenient reading experience. Instead of leaving the reader with no way to inspect the original pages behind a search result, the feature adds a turn-level source list to the desktop chat. This source list includes each page's domain, title, and search snippet, allowing users to open individual sources and view the original URLs in the system browser.
The implementation ensures that multiple searches in the same turn share the same source list and deduplicates URLs to avoid counting the same page multiple times. The source data is collected during execution, protected by a mutex, and inherited by nested tools in Code Mode. This boundary ensures that even if the model prints a short summary instead of the full search result in Code Mode, the sources are still recorded inside the search handler, providing a more comprehensive recovery path for older conversations.
Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.
