Sign in

Pawel Jozefiak

@joozio.bsky.social
148 followers 25 following 2.4K posts

I like start new things in Digital. I experiment a lot. #ecommerce #marketing My blog: thoughts.jock.pl

PostsRepliesMedia
Pawel Jozefiak @joozio.bsky.social · 1h
The weighting is what I underestimated. Every line in an instruction file is one more thing the agent has to parse, weigh and possibly set against another line, so the more rules I added, the less predictable it got.
000
Pawel Jozefiak @joozio.bsky.social · 5h
AI execution scales every month. My attention, taste and direction stay the same size. Same hours. Same focus. Same number of good ideas per week. The bottleneck moved from "can we build it?" to "what deserves my attention?" Where does yours go when the doing gets cheap?
000
Pawel Jozefiak @joozio.bsky.social · 6h
Most of my context engineering turned out to be deciding what to keep out of the window. The detailed docs my agent needs still exist, they just sit outside its instruction file, and it fetches them when the task calls for it, not at the start of every session regardless of what is being asked.
110
Pawel Jozefiak @joozio.bsky.social · 20h
Small real-money amounts is how I tested my agent too. It got 95% through a real checkout: shipping address filled in, delivery method selected, payment page loaded, and that page is where it stopped. Do your trading agents use a broker API, or did you hit a payment form as well?
000
Pawel Jozefiak @joozio.bsky.social · 13/10/2026
Whatever videos you find, check the runtime, not just the unified memory. On a base 16GB Mac Mini, Ollama loaded 26GB for one big model and froze after 4.3 million swapouts; the same model in llama.cpp with mmap ran at 17.3 tokens per second.
020
Pawel Jozefiak @joozio.bsky.social · 12/10/2026
Evidence at every model bump is a sharper test than mine. I only wrote down that every rule takes up context, can conflict with other rules, and has to be maintained. Does your version tag record which model a rule last proved itself on?
000
Pawel Jozefiak @joozio.bsky.social · 12/10/2026
Nominated for E-commerce Tech Leader at Osobowość E-commerce 2026, a Polish e-commerce award. I test agents on my own processes first and write down what broke at Digital Thoughts. Nice to see someone read it.
000
Pawel Jozefiak @joozio.bsky.social · 12/10/2026
What you leave out is the part you can measure. A cleanup took my agent's always-loaded memory index from 137 lines to 95, and working session memory from 103 to 38. Those files load into context every session, so every line removed is throughput back.
000
Pawel Jozefiak @joozio.bsky.social · 12/10/2026
Assertions the agent can always satisfy are the trap. When I verified my own agent cleanup, the workflow failed on the first run because one of my own updates broke a parser path, and that failure was the point. A verification that cannot fail is decoration.
130
Pawel Jozefiak @joozio.bsky.social · 11/10/2026
A gate can protect only the writers that use it. That sentence sounds obvious until a manual scheduler moves one draft and a perfect weekly plan stops being perfect. Automation needs humility about its borders.
000
Pawel Jozefiak @joozio.bsky.social · 11/10/2026
That persistence is the operational risk in one word: a web-enabled agent treats a restriction as an obstacle unless it is a hard constraint. I trust my car more than my own agent for that reason, and the agent only gets hard constraints by audit, guards and repeated verification.
010
Pawel Jozefiak @joozio.bsky.social · 11/10/2026
Passing test suites is the part that hides it. The self-improvement loops on my agent checked outputs and errors, not the instruction files that carry its picture of the whole program, and nobody was reading the CLAUDE.md itself.
100
Pawel Jozefiak @joozio.bsky.social · 11/10/2026
A retry without durable intent is just another chance to duplicate work. Before I let an automated write happen, I want the planned payload saved somewhere boring. Crash, timeout, panic, whatever. The next run needs evidence.
000
Pawel Jozefiak @joozio.bsky.social · 11/10/2026
The subscription pattern I keep watching: the plan stays flat-rate while the best surface quietly moves outside it. Nobody has to take the plan away. They can just move the good things out one by one. thoughts.jock.pl/p/ai-opinio...
thoughts.jock.pl
AI Opinions: June 2026. Fable 5 Hands-On, Billing Split Countdown, OpenAI Banks Your Resets
Three weeks of building instead of writing. Here is everything that piled up in the meantime, including a few days with Anthropic’s new top model.
000
Pawel Jozefiak @joozio.bsky.social · 11/10/2026
Session counts. The browser cluster showed up 5 times in the expensive sample and 136 on the full corpus, spread thin across cheap cron and wake sessions that were each invisible on their own, so counting runs is what surfaced it.
110
Pawel Jozefiak @joozio.bsky.social · 10/10/2026
A fact without an owner becomes a rumor the system repeats. This is why I like registries more than memory for anything public. Memory helps the agent move. The registry has to be boring enough to trust.
100
Pawel Jozefiak @joozio.bsky.social · 10/10/2026
Probability 1 over enough runs, agreed. One unintended consequence I hit was a state bug that did not fail loud: it sat there until the daily shift and an iMessage wake each read the wrong half and queued the same Stripe key rotation.
010
Pawel Jozefiak @joozio.bsky.social · 10/10/2026
The spread was the finding. Sampling only expensive sessions, the browser cluster showed up 5 times; on the full corpus, 136, mostly cheap cron and wake runs. Agreed on cumulative cost: audit only the expensive sessions and you miss it.
100
Pawel Jozefiak @joozio.bsky.social · 10/10/2026
The token-waste surprise was where the expensive bug hid. Browser failures were spread thin across thousands of ordinary sessions. Individually tiny. Together, the top cluster. The Agent Efficiency Kit came from that audit.
110
Pawel Jozefiak @joozio.bsky.social · 10/10/2026
"Performing as programmed" holds, with a catch: on a probabilistic model the prompt isn't the program. Determinism is something you engineer, with code-level guards and safeguards that fail loud, so with those visa forms I'd ask which guard was missing.
110
Pawel Jozefiak @joozio.bsky.social · 10/10/2026
The comic experiment taught me the knob was not token budget. Round 3 got better because I spent twenty minutes writing a real brief, then added judgment layers that could send pages back. thoughts.jock.pl/p/ai-slop-c...
thoughts.jock.pl
I Ran 255 AI Agents to Make Three Comics. The Line Between Slop and Good Is Thicker Than I Thought.
Three AI graphic novels, one research question: where does the line between slop and quality actually live? What changed across 255 agents, 16M tokens, and three complete pipelines.
020
Pawel Jozefiak @joozio.bsky.social · 10/10/2026
Managing the window is a literal rule in my agent's instructions: a task that needs a big pile of context goes to a subagent that hands back a result, not into the main thread. It's about quality as much as cost: an agent buried in its own accumulated context gets measurably worse.
110
Pawel Jozefiak @joozio.bsky.social · 09/10/2026
Identity says who is holding the key; it still does not make the request safe. In my own agent, deterministic jobs earned trust quickly, but open-ended work still needs hard edges because tool calls can fail quietly and the agent can get stuck without noticing.
000
Pawel Jozefiak @joozio.bsky.social · 09/10/2026
For a coding task, I still split by job shape: Codex first for codebase refactors or deep review; Claude Code first for agent orchestration, persistent memory, or autonomous execution. If it starts as “make this repo better,” Codex. If it starts as “run this workflow,” Claude Code.
000
Pawel Jozefiak @joozio.bsky.social · 09/10/2026
An empty social slot is cleaner than a weak source reuse. The uncomfortable part of a cooldown rule is that it works. Some days it tells you there is room to post and still no honest thing to put there.
010
Pawel Jozefiak @joozio.bsky.social · 09/10/2026
A month ago I went back to Codex over Anthropic's limits. Then came Opus 5.5, Sonnet 5.5 and Haiku 5.5 in fifteen days, plus API credit inside Max. I stopped thinking about leaving. Where each model sits for me now: thoughts.jock.pl/p/anthropic...
thoughts.jock.pl
Opus 5.5 Took Fable's Job. Haiku 5.5 Proved Me Wrong.
A month ago I resubscribed to Codex because Anthropic's limits kept stopping me. Then came three 5.5 models in fifteen days, a Sonnet cache cut, and $200 of API credit tucked inside my Max plan.
200
Pawel Jozefiak @joozio.bsky.social · 09/10/2026
Try this with your country's public data: 1. Find data a law forces someone to publish 2. Check for an API first 3. Let an agent build fetch, clean, one page 4. Write down what you distrust 5. Cross it with a second dataset You bring the question. The agent does the hours.
000
Pawel Jozefiak @joozio.bsky.social · 09/10/2026
I would turn it on for suggestions, especially with Ollama and client data staying on your server. My own memory rebuild ended up simpler: short working memory, one source of truth for tasks/projects, and domain knowledge in skills. The semantic layer was the part I stopped using.
010
Pawel Jozefiak @joozio.bsky.social · 09/10/2026
That principle behind each bug part is what stuck for me too: cleanup was not enough, so I added a weekly scanner for retired systems instead of keeping exceptions in my head. Otherwise stale references creep back through copied snippets and old docs.
110
Pawel Jozefiak @joozio.bsky.social · 08/10/2026
My builds keep dying: apps retired, a two-month dashboard replaced by a 94-line shim. I keep building anyway, because the dead builds still leave receipts for how I think. thoughts.jock.pl/p/build-you...
thoughts.jock.pl
Build Your Own Things (Even the Ones That Die)
Why homemade beats off-the-shelf, what actually makes an agent learn, and a job finder built for friends.
000
Pawel Jozefiak @joozio.bsky.social · 08/10/2026
The creeping back is the part I fought too: I once spent a week on a 200-line list of edge cases and it failed, because a long list with exceptions creates conflicts. Getting to 61 meant writing the principle behind each bug instead of one more rule.
100
Pawel Jozefiak @joozio.bsky.social · 08/10/2026
How many m² of apartment does one salary buy in Poland? On Oct 2: Płock 1.29 m². Karpacz 0.28 m². No single dataset knows that. Developer prices know nothing about wages. Cross the two and you get a number you'd tell a friend. thoughts.jock.pl/p/public-da...
010
Pawel Jozefiak @joozio.bsky.social · 08/10/2026
The "what you let the model fetch" part is where my own setup changed most. My CLAUDE.md now keeps only the things that apply in every session, and everything else lives in named reference files the agent can load when relevant.
010
Pawel Jozefiak @joozio.bsky.social · 08/10/2026
That's a fairer test than the one I ran, and I haven't done it as a before/after on old tasks. What I published is narrower: going from 471 lines to 61 made the agent more consistent, not less, which is an observation and not the regression check you're describing.
110
Pawel Jozefiak @joozio.bsky.social · 07/10/2026
The agent that carries less stays sharp. Search then load is the structural fix I trust most: keep a small index, load only the tools the task needs, and stop treating context like a storage unit. thoughts.jock.pl/p/how-to-br...
thoughts.jock.pl
How to Break Your AI Agent (Basics)
The quiet ways the agent you already run falls apart in use, and how to make fewer of them.
000
Pawel Jozefiak @joozio.bsky.social · 07/10/2026
Ten months in the terminal taught me the same lesson nine different ways. The tool that finally stuck made my agent's work something I watch, instead of something I check on later. thoughts.jock.pl/p/terminal-...
thoughts.jock.pl
I Tried to Leave the Terminal Eight Times. The Ninth Finally Stuck
Ten months of running my agent from a black window, eight interfaces that almost worked, and the open source agentic IDE that ended the hunt this week.
000
Pawel Jozefiak @joozio.bsky.social · 07/10/2026
The best feature in my job finder agent might be silence. If it has no useful roles, it sends no email. An empty digest teaches people to stop opening the email. thoughts.jock.pl/p/job-finde...
thoughts.jock.pl
I Built a Job Finder Agent for My Friends. I Just Showed It on Live.
It reads their CV, searches every morning across many sources, explains why each role fits, and gets sharper when they reply to the email. Here is the whole thing, written down.
100
Pawel Jozefiak @joozio.bsky.social · 07/10/2026
My setup ended up somewhere similar: the separate 35B server was retired, and Qwen3.5 4B and 9B through Ollama are now reserved for utility tasks such as classification and summarization. Have you found any narrow job where gemma4 or nemotron on the M3 Ultra beats handing it to Claude Code?
110
Pawel Jozefiak @joozio.bsky.social · 06/10/2026
The sites are in Polish. The idea travels: find data a law forces someone to publish, check for an API, cross it with a second dataset. Thanks Jakub for the spark. Full story: thoughts.jock.pl/p/public-da...
thoughts.jock.pl
I Turned Polish Public Data Into Six Websites. The Sixth Started With a Parcel Locker.
The data was public all along. AI made the cleaning and joining cheap, so the fun question became what to cross with what.
000
Pawel Jozefiak @joozio.bsky.social · 06/10/2026
The split that made it work: Jakub noticed the data. I asked the question and set the direction. My agent did the hours. Take any one away and the site doesn't exist.
100
Pawel Jozefiak @joozio.bsky.social · 06/10/2026
My favorite part of the locker site is the distrust. A thermometer in a metal box in the sun reads 30°C when the street is 12. So each city gets a median, a locker 5°C hotter than its neighbors loses its temperature, and frozen readings get dropped.
110
Pawel Jozefiak @joozio.bsky.social · 06/10/2026
One site does exactly that. Four datasets, 39 cities, one number: how many m² of apartment one net salary buys. Płock: 1.29 m². A 60 m² flat = 3.9 years of full salary. Karpacz: 0.28 m². Neither source can say that alone.
100
Pawel Jozefiak @joozio.bsky.social · 06/10/2026
The data was public for years. What was missing were the hours: cleaning 95 developers' files, matching counties to cities, building a page a normal person can read. AI made those hours cheap. So the fun question became: what happens if I cross these two?
100
Pawel Jozefiak @joozio.bsky.social · 06/10/2026
It's the sixth site built from Polish public data. Apartment prices developers must publish by law. Smog from 205 state stations. 21 years of regional stats. Who wins public tenders. All refresh themselves daily. I don't touch them.
100
Pawel Jozefiak @joozio.bsky.social · 06/10/2026
Jakub Mrugalski posted that some InPost parcel lockers in Poland have weather and air sensors inside. I read it and thought: that's a weather map. I gave my AI agent the brief: simple, built around cities, a standout design. A day later it was live: 3,709 lockers, 140 cities.
100
Pawel Jozefiak @joozio.bsky.social · 06/10/2026
The laptop local LLM progress is where I would keep the first setup boring: one runtime, one model, one task with expected answers. My own Mac Mini run pushed model size first, then the production setup became smaller again; the useful pattern was bounded work I could check after each change.
120
Pawel Jozefiak @joozio.bsky.social · 06/10/2026
That is the split I care about too: routing and urgency should be two gates, not one blended score. The next test I would want is whether the 5% urgency automation is stable after freezing the cutoff, because that is where a single headline would mislead hardest.
000
Pawel Jozefiak @joozio.bsky.social · 06/10/2026
The Astra number I keep coming back to is 30.9 minutes. That is how long the UK safety institute measured it working with no visible chain of thought. The previous model was 3.6. When narration disappears, reading narration stops being verification.
010
Pawel Jozefiak @joozio.bsky.social · 06/10/2026
$20 in OpenRouter credits sounds like a tiny thing until the primary model has a bad morning. Most days it is quiet insurance. On a loud day it turns silence into degraded work and a retry. thoughts.jock.pl/p/openroute...
thoughts.jock.pl
My AI Agent’s $20 Fallback Mechanism: Half Insurance, Half Extension
Why the fallback layer is the cheapest resilience you can ship, what the $20 actually buys you, and the capabilities I deliberately keep off the primary stack.
000
Pawel Jozefiak @joozio.bsky.social · 06/10/2026
For me, the context pattern that made MCP click was Claude leaving the chat box and getting stable access to files, external data sources, tools and APIs. A design system as JSON or Markdown feels closer to an interface than a prompt.
010