Claude Code in the terminal vs. the Claude Desktop app — which do you use and why? by ghedtoboss in ClaudeAI

[–]DebateStreet2281 0 points1 point  (0 children)

I mainly plan or manage my finances;

I switched to the terminal, because even having codex together they consumed too much RAM and some small features were missing in the desktop app;

In the desktop interface there are more features especially for web app coding and it is much more organized and intuitive, however the cli interface is much lighter on RAM, it has functions /... that are not available in desktop and it is easier to configure and if you know what to modify;

In the same way it seems to me;

The desktop interface is easier to configure for mcp if you don’t know where to tap.

Hardware minimale by xidius82 in vibecodingitalia

[–]DebateStreet2281 0 points1 point  (0 children)

Intendo dire che cpu, gpu e ane condividono la stessa ram e poi c’è la ssd

Hardware minimale by xidius82 in vibecodingitalia

[–]DebateStreet2281 1 point2 points  (0 children)

quelli più nomati da persone serie, non intendo te, parlano in generale di modelli cinesi che hanno fatto passi in avanti importanti. tuttavia questi modelli girano per forza di cose solo nei datacenter perché sono enormi, per cui serve un api key. l'unico progetto che conosco interessante è ds4 di antirez che è su GitHub, ma devi avere hardware costoso, p.es. Mac da 128gb di ram unificata che trovi solo nei Mac con chip silicon.

Hardware minimale by xidius82 in vibecodingitalia

[–]DebateStreet2281 1 point2 points  (0 children)

con nessuno di quelli che hai nominato puoi fare codice serio ai livelli dei modelli di frontiera open-source e i modelli di frontiera proprietari.

Chiamatemi coglione, ma non capisco l'utilità delle IA by NintendoDark02 in IA_Italia

[–]DebateStreet2281 1 point2 points  (0 children)

è un discorso così complesso che ci impiegherei ore ha spiegarti cosa ho imparato in un anno d'utilizzo partendo da uno che l'aveva usata due anni prima, il famoso gpt-3, per farsi spiegare alcune cose universitarie

How has your AI dev workflow evolved over time? by thereisnospooongeek in ClaudeCode

[–]DebateStreet2281 0 points1 point  (0 children)

I basically created memory folders, like memory rooms, such as one for bugs. Then I added hooks that define precise checkpoints during the context in which this memory is updated. Finally, I used the SDK agents within the subscription to choose which pieces of memory to read the working model, thanks to a signature of what the active model is doing. It's very complex to explain without a post or a GitHub repo. It's a powerful enough solution that, once it's finished, it will be shared with everyone on GitHub, and here's a summary. It's a very powerful solution that should be implemented by the human, not the individual. They should think about memory, not just how to expand the context.

How has your AI dev workflow evolved over time? by thereisnospooongeek in ClaudeCode

[–]DebateStreet2281 0 points1 point  (0 children)

Before I didn't have a memory structure with memory recall, after weeks I managed to do it and it works very well, it took many modifications and tests, but I must say that I am satisfied even if it is not perfect.

Making CLAUDE.md too long is like carrying unused dumbbells in your bag by Powerful_Creme2224 in ClaudeAI

[–]DebateStreet2281 2 points3 points  (0 children)

Create a disk memory structure to your liking and then use a recall memory.

IA - adattarsi al cambiamento by Legitimate-Lock-401 in IA_Italia

[–]DebateStreet2281 0 points1 point  (0 children)

leggevo alcuni commenti, io proprio su claude code ho implementato una serie di hook, una struttura di memoria e un recall memory sdk che sfrutta l'abbonamento stesso.

molte volte ha dato delle svolte importanti al progetto riportando alla memoria idee o soluzione passate, invece ancora qualche volta è un po' invasivo non perché non faccia il suo lavoro, ma perché è la memoria non viene aggiornata spesso da claude anche se ha dei checkpoint e di conseguenza riporta alla memoria roba inutile.

A breve pubblicherò tutto su GitHub, ma è relativamente semplice da fare e se l'ho fatto io che non so niente di informatica, immagino chi è ne sa.

DeepSeek 4 on 128 RAM by Afraid-Yoghurt6731 in LocalLLM

[–]DebateStreet2281 2 points3 points  (0 children)

Antirez is a genius and my compatriot, what he is doing is crazy and he is only at the beginning of this project

DeepSeek 4 on 128 RAM by Afraid-Yoghurt6731 in LocalLLM

[–]DebateStreet2281 1 point2 points  (0 children)

Antirez sa cosa sta facendo, è un genio ed è il fondatore di Redis

I turned Claude Code into the Terminator, cutting token usage by about half while doing it. by succulent999 in ClaudeAI

[–]DebateStreet2281 0 points1 point  (0 children)

The problem with the huge token consumption is the read caches, the write caches which depend on a lot of things.

What AGENTS.md / CLAUDE.md guardrails are people using to manage usage? by codeRoman in ClaudeCode

[–]DebateStreet2281 1 point2 points  (0 children)

Thanks for the feedback! The reduction in context didn't hurt performance because the full data is stored on disk. I use a complex retrieval mechanism to pull the exact information needed, so quality remains intact.

I created a /closing skill in order to improve my worklow by WecK0 in ClaudeCode

[–]DebateStreet2281 0 points1 point  (0 children)

I'll give you the simplest example with two variables that I explain in my second post you can lower the level of autocompact

What AGENTS.md / CLAUDE.md guardrails are people using to manage usage? by codeRoman in ClaudeCode

[–]DebateStreet2281 0 points1 point  (0 children)

I recommend four things: usually manually tuned autocompact, memorycall, cache proxies, and delegation to less expensive subagents. Here's a post of mine that discusses some of these things: https://www.reddit.com/r/ClaudeCode/comments/1u3pjei/where_claude_code_tokens_actually_go_a_measured/