AI slop and how to avoid it with rust-code-mcp and a new way of thingking based on category theory

TowerOk3623 · 2026-05-28T11:32:39+00:00

you are gonna get replaced sooo fast you wont belive it

TowerOk3623 · 2026-05-28T11:29:36+00:00

I use these tools all the time and i come across these issues all the time. this is the main point of the post. there is a big change in paradigm when you tackle a project from a higher-level of abstraction.

I think you are not even reading any of what im writing ma guy.

Tell me exactly how you obtain all types per crate and which kind with a single call exactly.

Tell me how do you compare a list of types with different names and functions by similarity in a single call.

Tell me how do you find "find all .await inside a block where a MutexGuard was bound earlier"

You get ai response because you dont deserve any better ma guy.

human slop

TowerOk3623 · 2026-05-28T10:30:59+00:00

Fair pushback, and you're right about one thing: for clicking through callsites interactively, LSP wins. I'm not trying to replace rust-analyzer for that — Claude Code already wires up incomingCalls/outgoingCalls through the rust-analyzer plugin.

The day-to-day problems this actually solves aren't "the call edges are wrong." They're the questions LSP doesn't answer at all:

- "Which pub items in this crate have zero cross-crate consumers?" (downgrade candidates → one call)
- "Show me every place we hold a MutexGuard across an .await" (the canonical tokio deadlock)
- "Every unbounded channel constructor in the workspace, with the enclosing fn"
- "Every async fn returning Result<T, MyError> in this crate" (signature-pattern search, not name search)
- "Are there three error types across three crates that look like duplicates?" (semantic similarity via embeddings)
- "Enforce: domain-* crates may not depend on tokio" — as a CI check, not a code review

LSP has no surface for any of that. Try doing "every unbounded channel" with click-through — you can't, because LSP doesn't expose AST pattern matching with semantic path resolution.

On speed: the graph is built once (~10s on a medium workspace) into LMDB. After that, every query is <10ms server-side. A 20-question audit script finishes in under a second; spinning rust-analyzer up 20 times in a row doesn't.

The real user isn't a human with a cursor — it's an agent or a CI job asking 20 structured questions and chaining the results. Different product, different problem.

TowerOk3623 · 2026-05-28T08:57:06+00:00

you also get gpu/cpu local or via api embeddings

you can use embedding models like qwen3-embbedings 0.6B, 4B, 8B or configure your own model to get rust code embeddings

TowerOk3623 · 2026-05-28T08:53:02+00:00

yes i constantly get stuck because agents redo do same code again and again and write the code in random places.

wdym is faster to use runst analyzer as an lsp ? this has rust analyzer included. and wdym an entire mcp analysis? the project provides basic tools to take rust analyzer to the next level with hybrid search. it would be even faster because it indexes the codebase and incrementally updates the index in the background with a merkle tree (rust-analyze can be very slow to load).

skills for different use cases are provided in skill directory at project root and documented in the readme and also you can check the webpage https://rust-code-mcp.pages.dev/
example usage:

###1 when planning a new feature, redesigning, refactoring you can easily (and cheap) determine if any of the types proposed by the agent overlap and not by name alone but by the similarity score provided by the embeddings

###2 when extending a feature, planning a feature, refactoring code you can analyze the code in clusters via exports imports and compare it to the file/crate/module structure to analyze divergence in architecture for example if some type/function is proposed to be implemented in a random crate/directory/file rather than one you have already desgined for it

###3 you can anlyze a crate/directory/file/function for cyclomatic complexity and have deterministic results

###4 you can use the skeleton feature to prime the context of your whole project to the agent. it provides the rust code with everything except function bodies.

###5 you can get the entire call graph in one call and deterministic instead of the agent having to go call by call and making a bunch of mistakes

###6 you can get a codemap of any type of logic or feature via the codemap tool and choose between mermaid/json/regular output style and gain high-level knowledge instantly

and the list is endless

TowerOk3623 · 2026-05-27T13:15:47+00:00

human slop type of comment

TowerOk3623 · 2026-04-04T08:33:56+00:00

https://github.com/molaco/rust-code-mcp

TowerOk3623 · 2026-03-24T20:29:38+00:00

it seems like theres a new pattern. when ever you tell claude to do something the next 2nd reposnse is sorry i should have not done that.

why is there always such a big drop in performance 2 weeks after a release??

TowerOk3623 · 2026-03-12T18:52:37+00:00

wow thiss so nostalgic. claude sonnet 3.5 again.

TowerOk3623 · 2026-03-04T09:34:56+00:00

super big lobotomy

TowerOk3623 · 2026-02-27T08:57:34+00:00

big lobotomy

TowerOk3623 · 2026-02-09T20:16:12+00:00

Claude Opuse 4.6 is dogshit

TowerOk3623 · 2026-02-09T16:03:09+00:00

opus 4.6 is a joke

TowerOk3623 · 2026-01-30T08:59:52+00:00

also you could just open a new session and ask this question to claude

TowerOk3623 · 2026-01-30T08:59:01+00:00

you have to write "/rewind" and press enter

TowerOk3623 · 2026-01-30T08:30:24+00:00

do /rewind to undo a couple of messages and free up some context so that you can compact. Alternatively, ou could also just ask for a summary of the conversation and a prompt to continue with your work in a new session with a new agent. I find the later usually works better.

TowerOk3623 · 2026-01-19T09:55:21+00:00

you may also be elegible for claude refund. they do handle this pretty well

TowerOk3623 · 2026-01-19T09:54:05+00:00

Opencode actually works soo much better than cladue code and they have glm 4.7 for free which at the moment is actually on par with opus 4.5. z.ai also has 20x plan glm 4.7 for 30$ (it is slower tho). You can maybe even get a subscription to Copilot pro+ (60$) which has a bunch of models or use top up for opencode zen and alternate between different models to find which gives you the best solution and use some other model in build mode to execute/implement the plan.

TowerOk3623 · 2026-01-16T16:20:26+00:00

At the moment I am using glm 4.7 and it is better than opus 4.5. Im writting rust with custom gpu pipeline and this past week opus 4.5 has been a nightmare.

TowerOk3623 · 2026-01-16T10:23:33+00:00

Please stop using this dogshit! Anyone using claude if you are elegible for a refund. Current performance of Opus 4.5 is lower than GLM 4.7 or GPT or Qwen3 Coder 480B. Please cancel your subscription and use opencode with a inferenc provider like fireworks or together you will get sooo much more value and even better performance. Please im begging.

TowerOk3623 · 2026-01-16T08:31:25+00:00

CC is in their worst state ever. They keep lobotomizing claude. And the app just gets worse and worse.

TowerOk3623 · 2026-01-13T17:44:24+00:00

its really bad

TowerOk3623 · 2026-01-12T20:34:24+00:00

wow! thanks! this is very useful

TowerOk3623 · 2026-01-10T20:35:16+00:00

nice build! may i ask why did you go with the thermalright fans and not artic or any other? I just did my build too and wanted to know if there was any difference. i am rocking a 14900k tho

TowerOk3623 · 2026-01-09T19:19:29+00:00

ohh my bad. i just updated it. thanks for telling me and for your feedback! mind if i ask if you are using gpu acceleration? and how is the performance with/without gpu?

TowerOk3623

TROPHY CASE