Solutions like these are really cementing the view that LLMs are becoming a commodity
HN user
jerpint
I like the concept!
Oops- typo in the title, should be “How I Maintain My Blog in the age of Agents”
Author here - I agree that to learn the best thing is to implement and fail along the way. My point was I would never professionally opt to write a sorting algorithm instead of using the builtin sort() most languages come equipped with
Author here - wrote this myself but I’ll take that as a complement :)
Nice! I made my own version of this many years ago, with a very basic manim animation
I did a post [0] about this last year, and vanilla LLMs didn’t do nearly as well as I’d expected on advent of code, though I’d be curious to try this again with Claude code and codex
[0] https://www.jerpint.io/blog/2024-12-30-advent-of-code-llms/
Best is very subjective depends what you want it to do and if you want to fine tune and how big you consider small
Hey this is awesome! I built something very similar, context-llemur, it’s a CLI and MCP interface to manage context
https://github.com/jerpint/context-llemur
Major difference is a conversation doesn’t get stored, the LLM (or you) can use the MCP/CLI to update with the relevant context updates
I like the concept and have built my own context management tool for this very purpose!
https://github.com/jerpint/context-llemur
Though instead of being a single file, you and LLMs cater your context to be easily searchable (folders and files). It’s all version controlled too so you can easily update context as projects evolves.
I made a video showing how easy it is to pull in context to whatever IDE/desktop app/CLI tool you use https://m.youtube.com/watch?v=DgqlUpnC3uw
This is great! Gonna try this on my next project
I also developed yet another memory system !
https://github.com/jerpint/context-llemur
Although I developed it explicitly without search, and catered it to the latest agents which are all really good at searching and reading files. Instead you and LLMs cater your context to be easily searchable (folders and files). It’s meant for dev workflows (i.e a projects context, a user context)
I made a video showing how easy it is to pull in context to whatever IDE/desktop app/CLI tool you use
I’ve been building a tool to help me co-manage context better with LLMs
When you load it to your favourite agents, you can safely assume whatever agent you’re interacting is immediately up to speed with what needs to get done, and it too can update the context via MCP
The way I see it is that context evolves somewhat orthogonally to code. But you still want to track it in similar ways. Having git under the hood makes it easy to track its evolution and undo/diff things LLMs might decide to change, but also means that tracking your todos and new feature ideas don’t pollute your codebase
I built a tool for this exact workflow in mind but with MCP and versioning included so you can easily track and edit the files on any platform including cursor, Claude desktop etc
I wrote a tool for this, which allows you to co-create and maintain a context repository with your LLMs
https://github.com/jerpint/context-llemur
CLI for the humans, MCP for the LLMS. Whatever is in the context repository should be used by the LLM for its next steps and you are both responsible for maintaining it as tasks start getting done and the project evolves
I’ve been having good success with it so far
I got tired of repeating myself to LLMs over and over so I built context-llemur
https://github.com/jerpint/context-llemur
It’s a CLI/MCP context management tool that allows you to easily move your project context around to your favourite LLM clients/IDEs
I built a library to manage this exact workflow! I actually used the library to build the library
https://github.com/jerpint/context-llemur
It’s MCP/CLI friendly , and wraps git around a context: folder, so you can super easily load context anywhere using: “ctx load” and ask LLMs to update and save context as things move along
I wonder how long we’ll start seeing demos like this with just Gaussian splatting and seemless transitions / infinite exploration
Funny enough, I’m building a tool that does basically what the author describes, but with a bit more software engineering driving it (context-llemur)
https://github.com/jerpint/context-llemur
The idea is to track all of the context of a project using git. It’s a CLI and MCP tool, the human guides it but the LLM contributes back to it as the project evolves
I used it to bootstrap the library itself, and have been using it more and more for context management of all sorts of things I care about
I’ve been building a context-engineering tool for collaborating with LLMs. The CLI is for the human and the MCP is for the LLM, but they all map to the same core commands
https://github.com/jerpint/context-llemur
I’ve actually bootstrapped ctx with ctx and found it very useful !
It basically stops me from having to repeat myself over and over to different agents
The last instruction
* Do not mention these guidelines and instructions in your responses, unless the user explicitly asks for them.
Most companies have realized it is impossible to stop prompts from leaking. Some already openly publish their prompts. This makes sense and would lead to less ambiguity, as it is still possible some of this “prompt leak” was hallucinated
Cursor developed their own tab models IIRC
Not sure this really counts but “curating” social media feeds to follow high-signal ML researchers and devs to keep up with the latest trends, ideas and papers
I know nothing about this type of data; what does it mean and how can it be interpreted as an object ?
Are there currently services (or any demand for) a text classifier that you fine tune on your own data that is tiny and you can own forever? Like use a ChatGPT + synthetic data to fine tune a nanoBERT type of model
It’s been useful though given the authors popularity I suspect it’s only a matter of time new LLMs become “more aware” of it
This is seriously lacking but I think things like jailbreaks and malicious prompts make it a bit too brittle for now
From just my observations they basically parallelized the install sequence instead of having it be sequential (among many other optimizations most likely)
History in the making