Vault

2.7K posts

Vault banner
Vault

Vault

@CallmeVault

Travel Photographer, Crypto Enthusiast, Web3 dev 🇵🇹

Portugal Katılım Aralık 2013
644 Takip Edilen1.3K Takipçiler
Vault
Vault@CallmeVault·
Here's the starter prompt — paste it into Claude Code to add a basic wrap-up to any project. 3 steps instead of 9. Grow from there. --- "I want a simple end-of-session wrap-up routine for this project. Keep it minimal — I'll grow it later. Create or update CLAUDE.md in the project root with this section: ## Session Wrap-Up When I say 'wrap up' or 'end session', run these 3 steps in order: 1. Capture decisions — Review our conversation and write a short bullet list of any architectural or design decisions we made this session (what we chose, what we rejected, and why). Append them to docs/decisions.md with today's date as a heading. Create the file if it doesn't exist. 2. Update CLAUDE.md — If any new patterns, conventions, or architectural rules emerged this session, add them to CLAUDE.md so future sessions follow them. Explain what and why, not just what. 3. Write a handover — Create or overwrite .claude/session.md with: date, what shipped (bullets), what's in progress (with context to resume), and a 'start fresh' note if nothing is in progress. Add .claude/session.md to .gitignore — it's local working state, not project history. Only run this sequence when I explicitly ask. Don't offer to run it proactively."
English
0
0
1
52
Vault
Vault@CallmeVault·
I used to lose hours every morning trying to remember what I did the day before with Claude Code. Not the code — the *reasoning*. Why I chose approach A over B. What was half-finished. What the next move should be. Then I built a 9-step wrap-up sequence. 5 minutes at the end of every session. Saves 30 minutes at the start of the next one. Full breakdown in the article below. Prompt in article first reply 👇 x.com/CallmeVault/st…
English
0
0
1
41
Vault
Vault@CallmeVault·
@CuteAndFunnyAlt That reminds me when in my country death certificates required renewal.
English
0
0
2
40
CuteAndFunny💢ᵃˡᵗ
CuteAndFunny💢ᵃˡᵗ@CuteAndFunnyAlt·
ID Verification every 3 months for people in the EU Because in 3 months time, you might turn into a minor!!! 🤡
CuteAndFunny💢ᵃˡᵗ tweet media
Paul Moore - Security Consultant @Paul_Reviews

Hacking the #EU #AgeVerification app in under 2 minutes. During setup, the app asks you to create a PIN. After entry, the app *encrypts* it and saves it in the shared_prefs directory. 1. It shouldn't be encrypted at all - that's a really poor design. 2. It's not cryptographically tied to the vault which contains the identity data. So, an attacker can simply remove the PinEnc/PinIV values from the shared_prefs file and restart the app. After choosing a different PIN, the app presents credentials created under the old profile and let's the attacker present them as valid. Other issues: 1. Rate limiting is an incrementing number in the same config file. Just reset it to 0 and keep trying. 2. "UseBiometricAuth" is a boolean, also in the same file. Set it to false and it just skips that step. Seriously @vonderleyen - this product will be the catalyst for an enormous breach at some point. It's just a matter of time.

English
164
1.9K
13.5K
503.9K
Vault
Vault@CallmeVault·
@BniWael Does it read .claude/claude.md ? Actualy full claude environment load? Also assume it works with monorepo too.
English
1
0
1
53
ProxySoul
ProxySoul@BniWael·
Ah shit, here we go again... → Opus 4.6 (SoulForge) vs Opus 4.7 (Claude Code) An older model just outperformed a newer one. How? Claude Code used 54.5% MORE context & costed more, produced more slop, lower quality code, and needed instruction files just to function. Why 54.5% more context? Read the article (in my profile) 😀 TLDR: Claude Code read full files and hoped to land in the right place. That's where the 54.5% goes. Meanwhile SoulForge knew where to find stuff, read surgically, knew how the codebase is shaped and avoided writing slop. I said it, and I will say it again. Models are no longer the bottleneck. Our tooling is. And it has not kept up with smarter models. SoulForge is almost there 👀 #claude #Opus
English
6
4
52
19.3K
Vault
Vault@CallmeVault·
@dejavucoder yeah, now creates code and adds lots of bugs compared to opus 4.6, run sonnet after and it finds the bugs...
English
0
0
1
136
sankalp
sankalp@dejavucoder·
is it just me or opus 4.7 has gotten dumber?!
English
94
10
517
45.5K
Vault
Vault@CallmeVault·
Solo founders don't have a team. They have time — and it runs out ... Horizon workflows: agent pipelines that scan, research, analyze, write, and publish on a schedule you set. You describe the workflow once. It runs while you sleep. #buildinpublic #indiehackers #AIagents #selfhosted
Vault tweet media
English
1
0
2
53
Vault
Vault@CallmeVault·
Paperclip and Openclaw had a baby. Meet Horizon, an AI team that turns business intent into execution.
Vault tweet media
English
0
0
1
65
Vault
Vault@CallmeVault·
Só pelo facto de terem sido empresas privadas a investirem no projecto vê-se logo de onde isso veio. Vai criar um sistema perverso onde as pessoas já pagam pelos resíduos sólidos e vão agora pagar também pelas embalagens. Vai incentivar o roubo de ecopontos. Vai ser prejudicial para o ambiente com viagens adicionais desnecessárias. Mas no fundo o objectivo era mesmo esse, era levar as pessoas aos pontos de recuperação. Enfim, uma trapalhada autêntica.
Português
0
0
1
46
dono da c🅾️🅾️perativa ™
dono da c🅾️🅾️perativa ™@donocooperativa·
Estado, a explicar-me as vantagens de eu deixar de meter algumas garrafas de plástico e latas no Ecoponto da minha rua, para passar a pagar mais 0,10€ por elas, separá-las, guardá-las, levá-las de carro e ficar na fila de uma máquina para recuperar o meu próprio guito. Ena.🥸
Português
87
128
1.2K
73K
Vault
Vault@CallmeVault·
@merlindotcom_ @Paperclip_AI @karpathy Just did the same today for mine. Not using paperclip. It’s a builtin from scratch system with persistent agents but the principle is the same. Could use your energy to help with my paperclip replacement ahah.
English
0
0
1
232
Michael Houghton 🐺
Michael Houghton 🐺@merlindotcom_·
day 23 of forking @Paperclip_AI today i added knowledge bases for projects and you company. based on @karpathy idea below. added a 'system chores' and 'agent chores' to manage memory. after each heartbeat run memories get added ('agent chores') and every 4 hours memeries get managed. This is in a db with an API for all agents to use and is seperated form the agents memeroes which they get at instantiation time.
Andrej Karpathy@karpathy

LLM Knowledge Bases Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So: Data ingest: I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them. IDE: I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides). Q&A: Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale. Output: Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base. Linting: I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into. Extra tools: I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries. Further explorations: As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows. TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.

English
18
6
163
17.9K
Vault
Vault@CallmeVault·
@airesearch12 Now all zero-day CVE’s have become a 7 day hacking party. 24-48h should be enough for most packages.
English
0
0
1
299
Nous Research
Nous Research@NousResearch·
The Hermes Agent update you've been waiting for is here.
English
339
472
5.1K
615.6K
Vault
Vault@CallmeVault·
Claude max x20 means limited to 20 prompts
English
1
0
3
72
Vault
Vault@CallmeVault·
@levelsio Agora já consigo perceber o que dizes
Português
0
0
0
60
Vault
Vault@CallmeVault·
Fundamental UX principle: don't let the UI become a proxy for AI thinking
English
0
0
0
49
Pavel Asparouhov
Pavel Asparouhov@Pavel_Asparagus·
Anthropic's usage limits have more to do with their usage than your usage
English
35
33
1.3K
51.7K
Vault
Vault@CallmeVault·
@altryne yeah, really sad.. we went from 2x to -5x this week. max plan x20 weekly gone in 24h to 48h..
English
0
0
0
27
Vault
Vault@CallmeVault·
Upgraded to Claude Max 20x this weekend. Was like buying a shitcoin at the top. @AnthropicAI @claudeai
English
0
0
0
70
Vault
Vault@CallmeVault·
@jumperz my claude week renewed yesterday and I'm already at 50% weekly limit.. wtf.. used to be 10-15%.
English
0
0
0
147
JUMPERZ
JUMPERZ@jumperz·
yeah, there’s obviously something wrong with Claude and you can’t convince me the opposite.. This was 3 prompts btw on Claude max
JUMPERZ tweet media
English
165
24
898
152.7K