wbmnfktr

ProcessWire is more alive than ever.

Fix is confirmed. Installed the latest version from Github and it's working as before. 🎉 GLM is pretty nice. Feel free to test it a bit more using that key.

This is the agent export dialog's result: glm-5.1 | <key_removed> | https://api.z.ai/api/coding/paas/v4 | Z.AI GLM 5.1 config->advanced=true; is set in config.php spaces before and after the pipe "|" look weird but are PW-style, so... no. Nothing incorrect. I created a full export, including the db, and put it up for download - I send you the link via PM.

AgentTools version 0.1.1 in ProcessWire 3.0.259 and 3.0.260 broke all agents in my current setups. Asking the Engineer only returns: ProcessAgentTools: API error (404): Not Found Added new agents (OpenAI-compatible and Anthropic/Claude): still no success. Only difference is, the ones with Anthropic (Claude) won't return the error message, yet no output or anything as far as I can see and tell. Update: Used the backup of version 0.0.9 - works in both instances with all agents.

You won't believe how these changes make my day(s) now! Moving away from ProcessWire to NextJS/AstroJS/HonoJs/WhateverJS just to be able to prove a concept and go live within a super short time using AI/LLMs/Agents was hard but I got things done. I was able to test things, to experiment, to explore, to fail, to succeed. Well... now ProcessWire is back. Back in my preferred stack of tools. Back on #1. I've already moved 2 big projects back from HonoJS and NextJS to ProcessWire. The RSS Monitoring Tool and another one. Cloudflare Workers and Vercel were great hosts with pretty awesome free tiers, yet... at some point I scratched limits big time. Now everything is hosted on H*stinger for a few dollars a month with full CI/CD pipeline, no limits on reads/writes to the database, just a 5GB size limit per database and some other weird limits those projects will never reach. It's unbelievable how fast things turned around and back to a language (PHP) I actually can read and understand and a framework I kind of know how to work with.

Can you define this a bit more detailed? I mean we have a lot of new AEO, GEO, LLMO, AIO, VEO, NEO, AISO acronyms out there. The name would suggest that NEO (Neural Engine Optimization) would be the focus... is this the case?

This will retire my whole set of ProcessWire skills... and I love it! I really enjoy the pace and direction you, @ryan, and ProcessWire are going now. Let alone AgentTools in a fresh installation of ProcessWire does some magic with LLMs (from super cheap Mistral, Deepseek, to great models like Kimi 2.6, MiniMax 2.6, and to Opus 4.6/7 and Codex 5.4/5) which was NOT possible in that way 6 weeks ago. 🥰

Had to pull the raw data for each session to answer this, but overall about $30 based on their (Z.AI) API pricing and the current free cache hits. I paid around $120 for one year of their Pro plan in a Black Friday deal. That's even sweeter.

That's amazing!

In Kilo Code there is this: You can set a model for each mode.

That's what I was thinking about. Like in other tools (Kilo Code Extension in VS Code in the screenshot). With this we come close to OpenClaw and Hermes territory.

What about being able to configure multiple models and then selecting the one for each specific task? Planning: Opus 4.x (or GLM 5.1, Kimi K2.5) Workload: MiniMax, Qwen, ... Most plans (I use) support Anthropic-, OpenAI-compatible, and custom endpoints. Right now we have Anthropic and OpenAI available (should cover 90% i guess).

Used Droid (https://factory.ai/) and OpenCode (https://opencode.ai/) in this project for now and they both had no issues at all (besides learning that the project is running in a DDEV environment). Also Z.AI GLM 5.1 and MiniMax M2.7 did a really great job. Not as fast (and by far not as expensive) as Opus 4.6 but planning everything in GLM 5.1, spawning subagents (only really works in OpenCode) with MiniMax that does the heavy lifting and then using GLM 5.1 again to confirm and double-check everything. 🤯

It also works without issues using MiniMax M2.7 - which is actually even faster. 🥰

YES!

Holy... this feels like a bit of Christmas and Easter on the same day during summer holidays. Just plugged Z.AI GLM-5.1 into this and ... From the side notes:

Ran into this issue here in another project using the latest version from the module directory. The file AgentToolsSitemap.php in the module directory is actually named AgentToolsSiteMap.php (capital M) and also renamed the class. I renamed the file and it seems to work for now. Also ran (not me, the agent) into some other issue.

I could swear that was playing at the gym today.

Various agents have various needs unfortunatelly. Not sure if this changed recently but in order to test my SKILLS I needed to create various folders (as symlinks) like: .agent .claude .cline .factory .goose .kilocode .kiro .pi .roo .windsurf Like for the ~/.config/ folder on Mac and Linux also the dot is necessary. Another option could be using the ~/.agents/ folder but here as well, not all agents support this yet.

Just created a new test project and added the module. One thing I noticed immediately was that in my DDEV environment I needed to prefix the commands in order to run them in the actual container. // non-DDEV environment php index.php --at-eval 'echo wire()->pages->count() . " pages\n";' // DDEV environment ddev exec php index.php --at-eval 'echo wire()->pages->count() . " pages\n";'

I'm happy to see you found your workflow using Claude Code. 🙂 A few things I'd suggest to make it a bit more future-proof and less focussed on one tool (Claude/Claude Code). I'm not sure if you use a CLAUDE.md file yet but in case you do or when you start using it, do this: In CLAUDE.md just add: @AGENTS.md And then write your instructions in/to AGENTS.md. The reason is simple: CLAUDE.md just works for Claude, but AGENTS.md works for almost any other AI agent. This way, either in a CLAUDE.md or AGENTS.md, you can customize comments in issues, like: ## GitHub issue and PR comments When responding in GitHub issue or PR comments: - Be concise, direct, and helpful. - Start with the answer first. - Use short paragraphs or bullets when useful. - Avoid unnecessary disclaimers, hedging, or repetition. - If the user asks for a change, give the exact action or code needed. - If more context is needed, ask one clear follow-up question. - Keep the tone professional, friendly, and technical. - Do not write long explanations unless explicitly requested. - Always add this as the last line in comments: [🤖 Answered by Joshi - Ryan's custom AI Agent.] Another thing you could change is updating the Claude settings.json to disable or customize the attribution line in commits and pull requests. https://code.claude.com/docs/en/settings https://code.claude.com/docs/en/settings#attribution-settings

The closest to a traditional setup for me would probably be: VS Code (or any fork or the Codium version) plus one of these extensions: Kilo Code, RooCode or Cline Coding Plan from either Z.AI or MiniMax.io VS Code an be installed almost everywhere without adding Node.js or other packages. The extensions can be installed from within VS Code but as they are quite similar, you should probably test them all. I kept Kilo Code as it felt to be the most stable and reliable one. Also Kilo Code offers additional features but only when using their subscription, for daily usage you can bring your own API keys and use those.

A little heads-up: WirePDF ≠ WirePDF I am in the process of upgrading a pretty old project, still running 3.0.240. I wanted everything up to date from ProcessWire to each and every module. So I was happy to see new version of WirePDF and went with it. Right after finishing the installation error messages showed up, Pages2Pdf broke and was messing with me, PDF generation threw errors, and so on. I started digging and found the problem: the listed update belongs to a totally new module called WirePDF (by @maximus) and has nothing to do with the file in the Pages2Pdf module folder. So there is a weird name collision and hijacking of the old module happening in the ProcessWire Upgrade (by @ryan) module right now.

Yeah, tried to fix that but it's not working out as expected. 🙈 Doesn't matter, the diff shows the changes pretty well: https://github.com/webmanufaktur/pwaiworkflow/commit/f0dba82a796881153ac6140aa9db70fdf2875d3e Updated that skill to have those advanced features.

That's a great find @gmclelland - I never use markup regions so wouldn't have noticed this at all. Ever. I compared the new details with the existing skill, this was the result: I guess we should add it. Right?