ryan

Greetings from Oslo, Norway. No ProcessWire updates this week as I'm currently traveling. The same will be true next week as well, but after that we'll be back to our regularly scheduled programming. I'm looking forward to getting back and trying out the new Kimi K3 model (in OpenCode Go) -- anyone had a chance to try Kimi K3 yet? It seems to have many of the YouTube AI channels excited. I'm also looking forward to checking out the new PAGEGRID 2.3 from @jploch, which sounds amazing. Have a great weekend and week ahead!

@Peter Knight Yes, I did a couple sessions with Sonnet 5 this week. It seems very good! Sonnet 4.6 is also very good (about the same for my use cases), and on my $20/month plan, I can use it most of the day and not hit any usage limits. As I understand it, Sonnet 5 cost is similar to Opus 4.8 once you take out the intro period and factor in how many tokens it takes to complete a task. I can't get much use of of Opus with my $20/month plan, so figured Sonnet 5 probably wasn't a good daily driver for me, except maybe during the intro period. Sonnet 4.6 is a great daily driver, especially on busy days. I also feel like I 'know' Sonnet 4.6 better than other models, having good rapport to the point where I can work more quickly with it. I know what to expect from it, its strengths and weaknesses, and like the areas where it tends to be more proactive. It mixes well with my workflow. When I need more horsepower, I really like GPT 5.5, which I use almost as much as Claude Sonnet. I get quite a bit of use out of GPT 5.5 on the OpenAI $20/month plan, but I do hit the 5hr limits with it more often. It's the one model that I can cautiously trust not to make mistakes. Like with Sonnet 4.6, I also feel like I know GPT 5.5 to the point where I can work with it more quickly. It has a unique sense of humor that keeps me chuckling all day. And it's got some funny quirks that I find entertaining. Like, it's got gripes and complaints about the the entitled compactor messing with its data. And it's sometimes got a hilarious fixation with gremlins and other mischievous creatures, where it treats the work we are doing a battle against those creatures. Tons of character. I also experimented with GPT 5.6 Sol and Terra this week also, which are impressive models. Despite those models being newer, it was clear that I'd have to spend a lot of time getting to know them well before I could get as much done as I can with GPT 5.5. I think it's because I'm still kind of a novice at this, and I'm not a vibe coder. I write code and collaborate with the model, so the rapport is more important to me than the technical details of the model. So far, GPT 5.5's sense of humor and quirks seem to be missing from GPT 5.6 models I've tested, but maybe it's just a matter of time. How about you, how are you liking Sonnet 5, and what other models are you using?

@Jonathan Lahijani I do find Claude really good with working through issue reports, and he almost doesn't need me to do them. If just one issue, I'll say "can you check out issue 1234". If we're going to do a batch of them, then I'll ask Claude to pick out a group of issue reports that we can work through without getting stuck. So Claude kind of pre-filters them to maximize the time we have to work with. He reads the report and suggests how he's going to fix it. I say go ahead, and he fixes it, pushes it, replies in the issue report, and closes it if appropriate, then moves on to the next one. It's a huge help. I still hand code a new module like InputfieldJson. But once I'm finished with it, I have both Claude and GPT 5.5 look over it and do a code review and make suggestions. For this I use AgentTools and my favorite models for writing API.md docs are GLM 5.2, Kimi K2.7 Code, DeepSeek v4 Pro, and of course Claude Sonnet 4.6. When I'm doing API.md files, I'll setup a scheduled task to run every 5 minutes and ask the agent to pick a class out of a list, and do a full code review and save to a .REVIEW.md alongside the class, then write API.md documentation and save to an .API.md alongside the class. (I point them to the HOWTO-API.md included with the WireApiDocs class). Once they've finished, they send me an email summarizing what they did. After several are complete, I ping Claude and he goes looking for new .REVIEW.md and .API.md files. He works through both, fixing any items found in the review, and verifying that the API.md docs are correct and complete. The .REVIEW.md file gets deleted once all items in it are accounted for. And Claude renames the .API.md to API.md after he's satisfied that it's as good as it can be. Then it gets handed off to GPT 5.5, which uses the API.md and class file to write WireTests for the class. GPT usually finds minor things to fix in either the class or the API.md after writing the tests. GPT is great at writing tests and fixing small details, but not so good at writing docs, in my experience. Whereas Claude is great at writing docs, but not as good with small details or writing tests. So they are a good pair to use together.

This week on the dev branch is ProcessWire 3.0.269. Highlights of this version include 32 issue reports resolved (even including some very old ones). 27 new API.md class documentation files were added. And 15 new WireTests files were added. Plus a new InputfieldJson module, WireHttpMulti class, and more. API.md files were added for these core classes: Wire, WireSaveableItems, Fieldtypes, FileValidatorModule, PageFinder, Pagefiles, Pageimages, Password, Process, Tfa, WireHttpMulti, WireTempDir, WireUpload, CliModule. API.md files were also added for these core modules: ImageSizerEngineIMagick, InputfieldDatetime, InputfieldJson, InputfieldPageListSelect, MarkupAdminDataTable, MarkupHTMLPurifier, MarkupRSS, PageFrontEdit, PagePathHistory, SessionLoginThrottle, LazyCron, WireTests, TextformatterMarkdownExtra New WireTests classes were added for these classes and/or modules: PageFinder, Password, WireApiDocs, WireHttpMulti, WireTempDir, WireUpload, ImageSizerEngineIMagick, InputfieldDatetime, InputfieldJson, InputfieldPageListSelect, MarkupAdminDataTable, MarkupHTMLPurifier, MarkupRSS, PageFrontEdit, TextformatterMarkdownExtra, plus 13 existing class tests were updated. New InputfieldJson module: a JSON-editing field, with API.md and tests. Now used by ProcessCommentsManager (for Comment meta data), ProcessPageEdit (opt-in editing of $page->meta() data, enabled in module settings), and ProcessModule (advanced-mode info viewer and config editor). In the page editor, see the new "Meta" input at the bottom of your Settings tab. New WireHttpMulti class (extends WireHttp): Enables concurrent HTTP requests via curl_multi, mirroring WireHttp::get()/getJSON(). Requires PHP 8.1+. Includes API.md and tests. (Via Matjaž Potočnik, @matjazp) Upgraded to the latest UIkit version for AdminThemeUikit: 3.17.11 => 3.25.19 New ImageSizerEngineIMagick sRGB conversion: When $config->imageSizerOptions['sRGB'] = true, converts wide-gamut images to sRGB before profile stripping. Bundles sRGB2014.icc. New Inputfield::collapsedIcon: Enables an alternate header icon when collapsed. For the next two weeks I have to do some travel and focused client work, so core updates will slow down temporarily, but we'll be back full steam ahead by the end of the month. Thanks for reading and have a great weekend!

@Peter Knight I think polite and/or positive language can have a place in prompting. LLMs are conditioned on the full prompt, including tone, social framing, implied collaboration style, etc. Maybe they don't feel encouraged the way humans do, but the language still changes the context the model is responding to. Research on emotional prompting suggests that motivational language can improve outputs, though it varies by model and task. Prompting an AI agent in a respectful, collaborative way (including perhaps saying "good morning") can be useful because it steers the kind of response you’re asking it to produce. Related and pretty interesting: EmotionPrompt improved results across different metrics between 8% and 115%.

@Peter Knight Not sure I understand? Are you talking about saying good morning?

@Joss it definitely sounds like a glitch in the forum. I logged into the admin earlier this week and it's not happy about the php version, it apparently wants 8.2 and we have 8.3, I think. So it could be that. But once I get back to the computer I'm going to see if I can figure out how to get it working.

@Joss hmm sounds like it didn't have permission to create the directories. You might check that processwire has write permission to site/assets. But if I recall correctly AgentTools will attempt to create them again when/if you use the scheduled jobs feature.

This week there were 45 commits on the dev branch for ProcessWire 3.0.268. The most interesting updates were: Added checkboxes in the Setup > Fields list, so you can bulk delete or export. Added new getRaw() and saveRaw() methods for WireCache ($cache) Added $page->meta() support to PagesExportImport export and import (via @jploch) Added WireTests test framework files and API.md documentation for the following, which finishes up the Inputfield modules: InputfieldTinyMCE InputfieldImage InputfieldFile InputfieldTextTags InputfieldSelector InputfieldPage InputfieldIcon InputfieldPassword InputfieldPageAutocomplete InputfieldHidden InputfieldPage InputfieldPageTitle InputfieldFieldset InputfieldMarkup InputfieldPageName InputfieldName InputfieldPassword InputfieldForm These were done using the AgentTools scheduled tasks Round-Robin feature that rotates between different agents. In this case, between DeepSeek v4 Pro, Kimi K2.7 Code, GLM 5.2 and Claude Opus 4.8. After each API.md and code review was finished, they were queued to GPT 5.5 who verified everything, made any necessary fixes, and then built a WireTests ClassName.test.php file for each. Following that Claude Sonnet 4.6 gave each API.md, ClassName.test.php and ClassName.module a final review and commit. In addition, we have a new version of AgentTools that adds the following: New MCP server support New WireTests coverage Improved CLI safety and migration checks New AgentTools logo added to README (design credit to GPT 5.5) There's also a new version of ProCache posted this week that adds CLI command support, AGENTS.md and API.md files, and fixes a few bugs too. As always, visit the ProcessWire Weekly for the latest news and updates. Thanks for reading and have a great weekend!

@JossI'm not sure I follow what you mean about "failed to create the subdirectories in jobs"? There is a /site/modules/AgentTools/tasks/ directory, where the predefined tasks are stored, is that what you mean?

Wow love that view! Nice look out the window too.

@Joss It won't let you upload a new one? Does it give you an error message or anything? We've been having some issues with the forums showing 500 errors when the bots start hitting, so it might be worth another try just in case the upload hit a 500 error. You can always send it to me and I can figure it out too. @Adam Kiss is another one to add to the list of people it would be good to see return.

@Joss Wow, that sounds like a nice hardware setup you've got there. And 128gb ram is like having a bag of gold right now, nice pirates booty. Have you tried Qwen 2.5 coder yet? Not a new model, but seemed pretty good when I tried it: https://ollama.com/library/qwen2.5-coder

@Joss Yes, on the "Agents" tab, enter a new Agent with the settings (replacing the model ID with whichever model you are using): Model ID: llama3.1 API key: ollama Endpoint URL: http://127.0.0.1:11434/v1 Label: Ollama llama3.1 The API key can be any non-empty value, like ollama, because Ollama usually doesn’t require one. AgentTools requires the field to be populated. The endpoint can be either one of these: http://127.0.0.1:11434/v1 http://127.0.0.1:11434/v1/chat/completions The model ID must match an installed Ollama model name from ollama list. Note that the Engineer relies on tool/function calling. So the Ollama model needs decent tool-call support, or it may answer text but fail to use eval_php, site_info, etc. For AgentTools, a coder/instruct model with tool support is the safer choice. Btw, if the connection works but Engineer behaves oddly, try a stronger tool-capable local model before assuming the config is wrong. Local Ollama can be great, but AgentTools asks a lot of the model because it needs reliable structured tool calls.

@jploch Good idea! It's been added.