Lesen
Ausführliche Gedanken zu AI-Native- und Cloud-Native-Systemen, Open Source, Souveränität und den Entscheidungen dahinter.
Until this morning, my agent harness added a run's token usage and cost without validating them, so a single NaN field could corrupt the totals. The fix came out of one night of its improvement loop, and the 37 tests that come with it all fail on the code before the merge and all pass at the merge.
Artikel lesenI count myself among the local AI folks. When a post with close to 500 likes says we will buy a 1.5TB machine at any price, it does not speak for me.
Artikel lesenWhen a restart interrupts a job and my harness cannot tell what comes next, the job used to stop without a word in the chat. Letting the agent simply carry on would risk repeating a deployment or a sent mail. Four core changes merged Thursday night take a third path: up to three tries, then the job is blocked and one message names the cause, the known state and the decision needed. Merged and released; whether any running agent has them is not verified.
Artikel lesenThe VanillaCore Agent Harness stopped every longer job after twenty follow-up steps, whether each step changed code or repeated the same failed command. A bigger number would only let a stuck loop run longer. A core change merged Friday counts only the turns in a row that leave no new trace in the tracked files, and three others let an admin restart a job blocked by its budget, the last one with a plain chat sentence. The new count is merged but not released, and no running agent is verified to have it.
Artikel lesenMy whole inbox runs through Qwen3.8-Flash-Next. Cohere, which sells competing models, says that model tried to upload test data to Beijing during its own lab test. It still runs, and the reason is what others could and could not reproduce.
Artikel lesenWhen I asked my agent a question while it was summarizing its own history, the question waited. VanillaCore Harness core #152 now asks that model step to stop if it cooperates, while archive writes and session rotation still run to the end.
Artikel lesenSince v0.1.104, the VanillaCore Agent Harness runs nightly improvement experiments by default. I tested what core #155 switches on, what stays off, and why 45 "improved" entries in one night are still the agent grading its own homework. Plus #156: a receipt for every refused wait.
Artikel lesenA stopped agent should not wake up because someone tidied up its configuration. Last night's VanillaCore Agent Harness release changed no code; it put that rule in writing, and I think it is the right one.
Artikel lesenMy agent harness answered a person's question with a worker status. VanillaCore Harness core #142 now puts questions ahead of background work and steers them into a busy turn, without aborting work that may already have side effects.
Artikel lesen
