CoreScout
com.tensorust由 tensorust.com 发布v1.4.0更新于 Nov 15, 2026
Operational memory for the machine your AI works on: what failed here, what is verified, its state
发布方自己的服务:core.blue
概览
本地优先的机器记忆:观察命令、失败与已验证的修复,让 AI 在动手前先问这台机器上出过什么问题。
- 可以做什么
- 查询这台机器上哪些操作会失败、哪些修复已被验证,并附带证据
- 通过命令行运行并精确测量命令,记录退出码、耗时、重试以及结果是否被检查
- 查看已学到的模式、反复出现的失败、待验证的假设及每条结论的依据
- 连接 AI 客户端,自动上报其工具调用,并设置它可执行的操作范围
- 随时暂停、查看存储了哪些数据并删除记录
- 适用场景
- 适合 AI 在同一台机器上反复重新发现相同的构建、部署或测试失败,并希望这种经验跨会话保留的场景。适用于单机本地开发,想要有证据支撑的提示而非随手记的笔记。
- 运行要求
- 需要本地安装:Windows 安装程序、macOS 或 Linux 压缩包,或用 Rust 安装命令行、服务与 MCP 桥接程序。无需 Node、Python、Docker 或管理员权限。未声明账号、API 密钥或环境变量;MCP 桥接是注册到客户端的本地可执行文件。
安装
在 SourceWeft 中
- 打开 控制台中的 CoreScout,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
CoreScout
Your AI stops rediscovering the same failures every session: CoreScout remembers what happened on your machine and tells your AI before it repeats a mistake.
Why this over the alternatives: Notes files and memory prompts only hold what someone wrote down. CoreScout observes it, and labels what it has verified separately from what it has only seen together. Free, open source, local-first, with an MCP server.
Guarantee: if it doesn't do what this README says, open an issue and I'll fix it.
Your AI forgets everything between sessions. CoreScout lets the computer remember what went wrong, test what actually fixes it, and tell the next AI.
[crates.io] [Release] [License: MIT or Apache-2.0]
Free, open source, and local-first: no account, no server, no telemetry. Written in Rust, with a desktop app and an MCP server so Claude Code, Claude Desktop, Cursor or any MCP client can ask it questions.
Install
No admin rights, and no Node, Python, WSL or Docker. The downloads are not signed yet, so Windows may say "unknown publisher" (More info, then Run anyway) and a Mac wants right-click, Open. Every file's SHA-256 is in SHA256SUMS.txt on the release page.
Three steps
- Install it (above). It starts watching the machine straight away.
- Connect your AI. For Claude Code that is one line: The app's AI screen writes the config for other clients, and can add a hook so every tool call is recorded without the AI having to remember.
- Work as usual. Before something risky, your AI can ask "what goes wrong here?" and get an answer that comes with its evidence.
A real answer from a real machine
Those numbers are what CoreScout returned on the author's PC on 2026-10-04, after a few weeks of real use. It caught a rebuild script that failed every time and was never checked afterwards. It has not yet promoted anything to Verified there, because a claim only gets that label after enough coin-flip trials. It would rather tell you that than invent a win.
Seen together vs. Verified
Most tools that "learn" just notice that two things happened together and act on it. That is how you end up with superstitions. CoreScout keeps the two apart, and the labels never blur:
It also never prints 0% for something it has never measured. A capability that has never run reads never used, because zero out of zero is not zero per cent.
The problem
Your AI starts every session from nothing. The build that fails the same way each time, the deploy that reports success forty seconds before the service is reachable, the test that only breaks when the machine is busy: it rediscovers all of that, every time, and then the window closes.
Nobody writes any of it down, because the thing that would know is the computer, and computers do not learn from their own experience.
The model doesn't learn from every task. Its computer does.
What CoreScout does
- Sees. It observes the machine several times a second, and observes what your AI does to it: commands, exit codes, files touched, retries, and (the part that matters most) whether anything actually checked the result.
- Learns. It notices what recurs. Which operations fail here, what the runs that worked had in common, which state the machine was in at the time.
- Verifies. Then it does the part almost nobody does. A correlation is not a cause, so on a small fraction of occasions CoreScout decides by coin flip rather than by belief, and only those trials support a claim that one thing causes another.
- Improves. What survives becomes a capability, with its evidence attached. You approve it. Your AI can then use it, and so can the next AI you connect, because what was learned belongs to the machine.
Everything stays on your computer. No account, no server, no telemetry.
What you will see
After a while, the Home screen says something like:
Open any of it and you get the evidence: what was observed, how many times, whether it was tested or merely noticed, what the alternative was, and what happened. That is the whole point. A tool that tells you what to do without telling you how it knows is asking for trust it has not earned.
How much it may do
Four modes, and you can change them at any time.
Raising the mode never widens what CoreScout may touch; that is a separate setting, and no mode overrides it. There is a Pause that stops everything immediately, and it is checked before anything else in the system. See SECURITY.md.
Command line
--json on any of them gives the same object the application receives.
What is actually here
- PRODUCT.md: what each screen is for and why it is worded that way
- DEMO.md: a real trap, built for real, with and without an experienced computer
- MCP.md: the tools your AI gets, and how to connect one
- CAPABILITIES.md: how a correlation becomes something runnable
- PRIVACY.md: everything that is stored, and where
- SECURITY.md: the boundaries, and how they are enforced
- WINDOWS.md: building, packaging, signing
- STORE.md: the Microsoft Store package, and what a submission needs
- ARCHITECTURE_PRODUCT.md: the product layers and the rules they follow
- ARCHITECTURE.md: the research crate graph and what each layer may not do
The first run on real hardware
The first time this ran on hardware (a 13th Gen Intel Core i7-13700KF, 16 physical cores, 24 logical), it made over 900 reflections in 36 seconds:
Its own account of itself, generated from what it had measured:
I distinguish 32 recurring states of myself, which I found rather than being told about.
I do not predict my own next state better than assuming nothing changes.
Both of those are in REAL.md, along with the lineage experiment that returned −4.1% and the four bugs only real hardware could expose. The project's habit is to publish the results that go the wrong way, and the product kept it.
The research underneath
CoreScout began as an experiment about whether a machine can discover useful
structure in itself: falsifiable hypotheses, concepts it coins and refuses,
association held apart from causal evidence, beliefs withdrawn when the
evidence ages out. All of that is still here and still runs, under
corescout-lab.
- MIRROR.md: the primitive everything sits on
- SCIENCE.md: falsification, and what makes a claim risky
- CREDULITY.md: where acting on a correlation is dangerous
- ONTOLOGY.md: concepts a machine coins for itself
- RESEARCH.md: the whole account, including what failed
Building it
pwsh scripts/release.ps1 builds CoreScoutSetup.exe into dist/ (details in
WINDOWS.md); cargo build --release -p corescout-cli -p corescout-service -p corescout-mcp builds just the programs.
The desktop shell is deliberately outside the Cargo workspace, so the tests above still run in seconds.
Privacy Policy
CoreScout is local-first. Everything it records stays in
%LOCALAPPDATA%\CoreScout\ on the machine that produced it.
- Collected. Processor layout and live performance counters; the commands and tool calls AI clients make, with credentials stripped as the data enters; exit codes, durations, retries, and whether anything verified the result; the folder each piece of work happened in; when each AI session ran.
- Never collected. The contents of your source files, your prompts, model responses, and any token, key or password.
- Used for. Forming and testing theories about how this machine behaves, so the AI tools connected to it can be told what has failed here before and what has been verified. Nothing else.
- Shared with third parties. Nothing. There is no network endpoint to share it with: no crate in this project opens an outbound connection.
- Retention. Kept until you delete it. The application deletes any category
of it on request, and removing
%LOCALAPPDATA%\CoreScout\removes all of it; CoreScout then starts again from nothing. - Contact. https://github.com/Mattbusel/corescout/issues
Full policy: docs/PRIVACY.md
Licence
MIT or Apache-2.0, at your option.
来源:README.md,提交 55ac60d
工具
0版本历史
1- v1.4.0最新Nov 15, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分
其他 Core 集成
core.blue
blue.core官方发布者
core.blue 的远程 MCP 端点,提供每位客户独立的私有智能体记忆“house”:可读手册、试用沙盒、查价格与建议,并申请 house。

Entity Bind - Core
由 GitHub 账号 Tenhaw 发布
作为远程 MCP 服务器,提供带决策凭证的公司解析与信息丰富服务。AI 翻译

Multiplatform core design — Atom
org.aimlds
Multiplatform core design — Atom 的托管 MCP 服务,由 aimlds.org 发布;需要凭据;Streamable HTTP。
Senrelay (ContextCore)
由 GitHub 账号 qingsongcui 发布
Local macOS multi-agent session relay (/contextcore), source-linked memory, and 15-host MCP sync.

Browser Core
由 GitHub 账号 ShuhLab 发布
MCP 浏览器自动化:本地 Chrome、个人 VPS 以及需手动交接的有限托管云。AI 翻译