My AGENTS.md

[mLipok]

57 minutes ago, corz said:

But the harness must attach this to EVERY prompt, along with whatever context you have already accumulated, which may be a lot.

What you mean here ?

 

[corz]

18 minutes ago, mLipok said:

What you mean here ?

 

Like an HTTP request, an AI model has no "memory"; text goes in, text goes out, and that's it (which is why we need cookies in browsers, otherwise every page would treat you like a new visitor and start from scratch).

One of the harness' main jobs is to provide this memory. So instead of the model seeing, "So just how tall is he then?", with no clue as to what you mean, the harness feeds it all the previous conversation, "Who played Darth Vader in the original Star Wars movies? / David Prowse played the physical part while James Earl Jones did the voice work / <that question here now makes sense>". The model now understands the "context" (which is fed via a different part of the JSON request so the model understands how to treat those data Vs your new prompt). 

Different harnesses  - every frontier model we interact with online has a harness in the "middle", providing context  (what has already been said in the conversation) as well as, in a local context; "instructions", the AGENTS.md and other files our harness uses to guide the model - do things slightly differently.

But basically, along with EVERY SINGLE prompt you fire at your model, the harness needs to inject the FULL contents of your AGENTS.md. Every time. Every single prompt.

Normally this works great. BUT, if your context gets huge, the AGENTS.md gets forgotten, or at least becomes, less important, in the growing mass of data.

You do not want this. That's why a fresh "chat" (zero context) is usually the best way to start a new task.

[corz]

More AGENTS.md related observations...

A model is more than happy to work with you on making its own AGENTS.md more efficient, and therefore productive. They see this as a win, as do I.

I was flippant, earlier, saying "Get AI to do it!", but this is actually by far the best strategy. 

It's difficult to describe the perspective/stance models take when tasked with this. They become detached, now looking at any previous failed output as a failure in their AGENTS.md, which they will now fix for you. As they add this new "functionality", they will scan for other directives which might conflict, or coalesce nicely, or whatever. So another win-win.

NO-ONE knows reading AGENTS.md like AI does, as they get the bloody thing with EVERY SINGLE PROMPT.

[corz]

This is a broad one, and it's definitely something you can plumb into your AGENTS.md, and better yet to simply be aware of it..

Recently, AI models have become much more "Goal Orientated", in that the goal seems to be the driving factor. Their attention span has increased dramatically, context awareness, the ability to handle long tasks, and this has led to an increased ability to follow a particular goal.

We can use this shift to our advantage to save a lot of time. I spoke earlier about how AI respond to being given agency and freedom, but these are in service of "the goal". The better you get at defining your goal, the less work you will need to do, simple as that. Back-and-forth with your agent is a dead end. If you find yourself there, you fucked up. Start afresh. As for "planning", that's getting less and less relevant.

You can spend fifteen minutes writing a spec and laying out every detail (which you, puny human have not thought through thoroughly!) and the AI, now in slave mode, will do your bidding. But this produces sub-par results.

MUCH better to say, "Hey, I want THIS THING. Define *exactly* the thing YOU WANT, not technical details (it has read more manuals than you), not nickety UI details (it has seen more UI's than you), not code pathways or any bullshit like that, just, as a "user", state what you want, what your expected results are.

Recently I've started writing simple documentation passages explaining the (not yet created) feature or function and then saying, "read that, that's how X function should work for the user. Make it so!". You might need to sweep up a few deatails afterwards, "Man! We already have a function that does almost EXACTLY THAT!", but way less time than writing a big spec in the first place. Your agent will likely surprise you with edge cases and pathways you hadn't considered. Some might even be valid!

Remember, it's read all the manuals, seen all the conventions in action, read every question and follow-up comment. Trust me, no matter how good you think you can code, with some intelligent steering (where your input actually matters), your AI assistant can do it better, and a thousand times faster.

As stated often, you still need to be there, at this time. It will do stupid stuff, it will create functions where duplicates already exist, it will, on a simple suggestion, convert every single variable in your program to a defined constant at the top of your script (oops!), ANYTHING. So for now, no way you can ship code if you don't already know code. But very soon, even that won't matter.

And I think this is the place where "coders" are finding trouble letting go. Just let go!

The sooner you accept that yours is now the realm of "Ideas", the better "your" code will be.

Or else just do it for fun, and it is fun, except a thousand times slower.

[argumentum]

26 minutes ago, corz said:

Hey, I want THIS THING.

..I should be "safe" and backup the source to a subfolder named `BackUp` with the same name and add *_oldN.au3. Feel like coding just that one function with headers ?

Here is the function complete with standard AutoIt UDF headers and error handling. Drop it right into Au3Align.au3 and call it before rewriting your code file.
 

Spoiler

expandcollapse popup

#include <File.au3>

; #FUNCTION# ====================================================================================================================
; Name...........: _BackupSourceFile
; Description ...: Creates a numbered backup (_oldN.au3) in a 'BackUp' subfolder relative to the source file.
; Syntax.........: _BackupSourceFile($sFilePath)
; Parameters ....: $sFilePath - Full path to the source file to back up.
; Return values .: Success - Returns the full path of the newly created backup file.
;                  Failure - Returns "" and sets @error:
;                  |1 - Source file does not exist.
;                  |2 - Failed to create 'BackUp' directory.
;                  |3 - FileCopy failed.
; Author ........: AutoIt Developer aka argumentum 😅
; ===============================================================================================================================
Func _BackupSourceFile($sFilePath)
    If Not FileExists($sFilePath) Then Return SetError(1, 0, "")

    ; Split path into drive, directory, filename, and extension
    Local $sDrive = "", $sDir = "", $sFileName = "", $sExt = ""
    _PathSplit($sFilePath, $sDrive, $sDir, $sFileName, $sExt)

    ; Target backup directory relative to the source file
    Local $sBackupDir = $sDrive & $sDir & "BackUp"

    ; Ensure BackUp directory exists
    If Not FileExists($sBackupDir) Then
        If Not DirCreate($sBackupDir) Then Return SetError(2, 0, "")
    EndIf

    ; Find the next available _oldN sequence index
    Local $iIndex = 1
    Local $sBackupPath = ""
    Do
        $sBackupPath = $sBackupDir & "\" & $sFileName & "_old" & $iIndex & $sExt
        $iIndex += 1
    Until Not FileExists($sBackupPath)

    ; Copy source to backup path ($FC_OVERWRITE = 1)
    If FileCopy($sFilePath, $sBackupPath, 1) Then
        Return $sBackupPath
    EndIf

    Return SetError(3, 0, "")
EndFunc

and I added it to au3align.au3 script.
It didn't code it as I would have but it is sound code. So yes, "AI assisted" coding is faster. And the day I jump on agentic/vibe coding, it should be simple as long as I approve the code, because an "auto compete on cocaine", still an auto-complete, even if coked up  

[argumentum]

3 minutes ago, argumentum said:

an "auto compete on cocaine"

..I know that is more than that but is a befitting over-over-simplification   

[corz]

I FUCKING HATE auto-complete, and it is the first thing I disable on a new editor (not for a long time now, I like Notepad++)

I always felt it interrupted my FLOW. I KNOW what I want to type! 🙃

Likewise Clippy and his companions, they made me want to reach into the screen, and strangle.

This is a whole new ball game. It IS auto-complete, in a sense, but at the same time, totally different.

Auto-complete is simple pattern recognition.

THIS is, erm, COMPLEX pattern recognition!! lol

I touched on this earlier, the idea of building all these coding/maths/science/etc. geniuses atop LLM was 100% the way to go.

They "get" your vibe, which is what makes all this possible. Anyone could write a fine AutoIt script these days and that is, to my mind, a WONDERFUL thing!

[bogQ]

On 9/21/2026 at 3:34 AM, corz said:

 

Fuck Ollama!

When i was starting to play with LLM-s locally I was unsuccessful for weeks to run LLM on Windows on my AMD 9060 16GB with Ollama. No matter what I tried (i had adrenaline, ROCm), everything was still allocated only to my system ram.

So after some time pain I decided then to try the same with LM Studio for local LLM-s and on first try magic happened  . LLM-s started to initialize AMD GPY memory on first try  It was slow do not get me wrong, we are talking about 16GB low end AMD graphic, but god dam it it was allot faster than using model from system ram instead. It even balanced some load from GPU and to ram if memory on GPU did not have capacity for that model. In the end 16GB-GPU and 64GB-RAM= allot of models I can load to test and play with.

 

[argumentum]

..this video on youtube "You're Using AI Completely Wrong" that has that "click bait" naming is actually nice. Simple explanations. The 1st 12 minutes, meh, but thereon after, interesting chat these 2 guys have. The link above starts at that 12th minute onwards.

[corz]

23 hours ago, bogQ said:

When i was starting to play with LLM-s locally I was unsuccessful for weeks to run LLM on Windows on my AMD 9060 16GB with Ollama. No matter what I tried (i had adrenaline, ROCm), everything was still allocated only to my system ram.

So after some time pain I decided then to try the same with LM Studio for local LLM-s and on first try magic happened  . LLM-s started to initialize AMD GPY memory on first try  It was slow do not get me wrong, we are talking about 16GB low end AMD graphic, but god dam it it was allot faster than using model from system ram instead. It even balanced some load from GPU and to ram if memory on GPU did not have capacity for that model. In the end 16GB-GPU and 64GB-RAM= allot of models I can load to test and play with.

 

Nice. LM Studio is good. IIRC, under-the-hood, it uses llama.cpp!

[corz]

15 hours ago, argumentum said:

..this video on youtube "You're Using AI Completely Wrong" that has that "click bait" naming is actually nice. Simple explanations. The 1st 12 minutes, meh, but thereon after, interesting chat these 2 guys have. The link above starts at that 12th minute onwards.

I don't do instruction videos!

Is there a web page version?