You really should either just write it manually, or at least clean it up, 5kLOC of bash for POSTing and reading/writing files is a bit overkill (the code is extremely repetitive, verbose and just hard to follow).
Yes, the code is big and bulky, i know.
But i am a single person, not a team.
I write simple and clear for me, because i need to mantain it.
Only Bash, zero dependencies, i like this.
Architecture and structure are my decisions, LLM are instruments, simple executors, today i think are commonly used.
Write code with LLM is not "push a button", it's a technical way of work, needs study and practice.
5k lines are months of work, debug, refactor, testing.
5k lines are the result of a long (and difficult) work, but LLM helps your productivity.
The most important thing, for the humans, are the architectural decisions, and understanding how your current LLM reasoning and behavior.
I decide architecture and structure; LLM only writes code (that need debug and testing), LLM are executors, not automatic.
LLM are only software, and are new instruments to learn.
Important thing: I use only free plan, of LLMs that have a real free plan.
I agree. What is with the random precore/core stuff anyways. But on the flip side, this thing seems to be doing a lot. I chugged through a couple thousand lines and there seems to be some amount of context management, I saw mentions of a history file, attachments, etc.
The macro sections/sections/sub-sections in the code are not random, I intentionally decide that.
In brief:
PRECORE_BOOT - for initialization
PRECORE_RUN - persistency, history, cache
PROVIDER - embedded provider (groq)
CORE_SETUP - global runtime configuration, parsing parameters, LLM whitelist, user configuration
CORE_PROVIDER - providers validation, prompt assembly, chat sessions, models tuning
The macro sections has two functions:
1, for me, to navigate the code
2, for LLMs, to understand my structure
The project does many things, so i need a clear sections structure to separate responsibilities.
You can see more information on the documentation, but the architectural spec is only in Italian.
. Portable - You need only: bash, coreutils, findutils, util-linux, gawk, curl, jq.
No Python (slow), no Node (heavy), no Golang (need too many binaries, one for each OS, hard to maintain for one single person like me).
. Single file - only one. I write many extras, but all are optional.
. Idempotent - you copy it where you want and go!
. Transparent - open the file and read.
. Extras for all, and all optional: help file, extra providers, improved session engine,
small GUI/CGI, etc...
Default (embedded) provider is Groq, because when I start the project, was the best free API service for AI.
I'm ready to answer to your question... with my terrible english...
thank you for your comment!
You mean the LLM writes the code based on your instructions (that's fine, I guess, but 5KLOC is huge for this kind of script).
It's certainly not because you are proud of yourself, it has been generated.
So I genuinely wonder why?
The macro sections has two functions: 1, for me, to navigate the code 2, for LLMs, to understand my structure
The project does many things, so i need a clear sections structure to separate responsibilities.
You can see more information on the documentation, but the architectural spec is only in Italian.
. Portable - You need only: bash, coreutils, findutils, util-linux, gawk, curl, jq. No Python (slow), no Node (heavy), no Golang (need too many binaries, one for each OS, hard to maintain for one single person like me).
. Single file - only one. I write many extras, but all are optional.
. Idempotent - you copy it where you want and go!
. Transparent - open the file and read.
. Extras for all, and all optional: help file, extra providers, improved session engine, small GUI/CGI, etc...
Default (embedded) provider is Groq, because when I start the project, was the best free API service for AI.
I'm ready to answer to your question... with my terrible english...
Cristian (kamaludu)
I'm also very doubtful performance of this would be faster than python, bash is very slow.
We invited the user to rewrite it and I've moved that text to the top now, and re-upped the post so it gets its full time on /newest.