Jump to content

wbmnfktr

Members
  • Posts

    2,236
  • Joined

  • Last visited

  • Days Won

    59

Posts posted by wbmnfktr

  1. Had a bit of fun with the latest DEV version and AgentTools version... yet ran into some issues.

    1. I asked the Engineer to get a good grasp of the project, explained what it was for and what the Engineer should look at. Got this response:

    2026-05-12_20-23.png.ace89ba5edc59dc460ca42d380d51aec.png

    Refreshed the page, waited a bit and got what I was looking for. The result was on point and the next task was executed without issues, it wrote a migration and what i was looking for.

    2026-05-12_20-31.thumb.png.d5fb1a3efbfe84a8c32feb0244ab55f6.png

     

    2. A bit later I asked the Engineer to answer a question I found here in the forums and got:

    2026-05-12_21-19.thumb.png.2c15aa59aaf34a966acf00a202804e08.png

     

    Every request was using GLM 5.1 which can run long tasks and has tons of tools calls it can process.

     

    Just some findings I wanted to report.

  2. On 5/2/2026 at 3:43 PM, Peter Knight said:

    Not sure if this answers your question or if I misunderstood? 

    That answers my question perfectly fine. You understood me here.

    • Like 1
  3. I feel that!

    But it became way better than it was a few years back when the world was going nuts.

     

    The things I changed in the last 12-18 months:

    • getting all the regular vitamins and supplements for someone my age
    • getting additional supplements that help my brain to keep working
    • checking in on gut health and eating less/none heavily processed foods
    • checking calories and protein in-take - fixing both and removing empty carbs and calories
    • getting back to the gym - first only cardio, now additional strength training

    All the above helped me to not being stressed out everytime and all the time.
    I couldn't care less about things thrown at me these days.

    A full day with meetings, a workshop, and a coffee with friend somewhere in-between, and of course the usual time at the desk don't affect me in a negative way anymore.

    I don't know how the math works here, but these days I have enough hours each day to have plenty of time, even time to balance everything out. PLUS the weekends for side-projects, fun, friends, family, and just things.

    • Like 2
  4. Fix is confirmed. Installed the latest version from Github and it's working as before. 🎉

    7 hours ago, ryan said:

    ... using your GLM info and sent just one prompt to it, see below. (GLM seems nice!)

    GLM is pretty nice. Feel free to test it a bit more using that key. 

    • Like 1
  5. 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

    1 hour ago, ryan said:

    See if anything looks incorrect in the raw config json ?

    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.

  6. 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.

    image.thumb.png.a8795d7a30efc4a1bca3096c4cbc187f.png

     

    Update:
    Used the backup of version 0.0.9 - works in both instances with all agents.
    image.thumb.png.8eca30b698d7fff552160e6182fc9442.png

  7. 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.

     

    • Like 8
  8. On 4/30/2026 at 11:17 AM, Peter Knight said:

    module built for today's SEO

    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?

  9. 1 hour ago, ryan said:

    Now all core classes that will receive their own API.md documentation also have their own directory. The /wire/core/ directory kind of resembles the /wire/modules/ structure now. In addition, new API.md files have been created for the Pages, Page, PageArray, Modules and Module, all of which also improve the online API reference documentation too, which is what those links are linking to. We'll continue adding more API.md documents every week.

    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.

    🥰

    • Like 7
  10. 1 minute ago, ryan said:

    maybe a select/drop-down under the engineer prompt box where you can select the model to use

    That's what I was thinking about. Like in other tools (Kilo Code Extension in VS Code in the screenshot).

    2026-04-18_01-44.png.e3e9d2904d259ef40c65d60b27fc71d7.png

    3 minutes ago, ryan said:

    And we should be able to share memory between them too, once it's added.

    With this we come close to OpenClaw and Hermes territory.

    • Like 2
  11. 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).

    • Like 5
  12. 9 minutes ago, ryan said:

    I'm thrilled to see the AgentTools module working with another AI Agent.

    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. 🤯

    • Like 2
  13. 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 ...

    2026-04-18_01-00.thumb.png.3c6d8ca274dc0a886664ef4130ddbb60.png

     

    From the side notes:
     

    Spoiler

    The whole project was migrated from Hono, React, Vite, Cloudflare Workers with D1 just by using AgentTools in the last couple of days.

    From this:

    2026-04-15_20-01.thumb.png.9ee402f14de7834b86fd64deab8695a1.png

    To this without me adding or creating any template or field:

    2026-04-15_20-00.thumb.png.b3c21df4706661cdcc04165a17413625.png

    2026-04-15_20-00_000.thumb.png.8ac7a36e6f327b987781e393b2916c5a.png

    2026-04-15_19-54.thumb.png.70b04c6c2a0c1c349da4c88deec301d1.png

    Took around 5 hours for the inital migration (Droid with GLM 5.1) and another 3 for frontend and a little bit of fine-tuning (OpenCode with GLM 5.1). Around 170,000,000 token in total so far.

    2026-04-18_01-08.png.5dbe1603b26db722226c329709de03ff.png

    That was a fun ride!

    I might never touch NextJS or similar again now.

     

    • Like 9
  14. Ran into this issue here in another project using the latest version from the module directory.

    Quote

    Warning: include_once(/var/www/html/site/modules/AgentTools/AgentToolsSitemap.php): Failed to open stream: No such file or directory in /var/www/html/site/modules/AgentTools/AgentTools.module.php on line 243

    Warning: include_once(): Failed opening '/var/www/html/site/modules/AgentTools/AgentToolsSitemap.php' for inclusion (include_path='.:/usr/share/php') in /var/www/html/site/modules/AgentTools/AgentTools.module.php on line 243

    The file AgentToolsSitemap.php in the module directory is actually named AgentToolsSiteMap.php (capital M) and also renamed the class.

    2026-04-10_02-34.png.142470170553f3335544a6a8986ab969.png

    I renamed the file and it seems to work for now.

     

    Also ran (not me, the agent) into some other issue. 

    Spoiler

    AgentTools Issues

    --at-sitemap-generate not accessible from --at-eval

    Problem

    The sitemap can only be generated via the dedicated CLI flag:

    php index.php --at-sitemap-generate    # works
    

    But calling it from --at-eval fails:

    php index.php --at-eval 'wire("at")->sitemap()->generate();'
    # ERROR: Method AgentTools::sitemap does not exist or is not callable in this context
    

    Root cause

    $at->sitemap is a property, not a method. AgentTools::get('sitemap') returns an AgentToolsSitemap instance via the helper system (line 316–319 of AgentTools.module.php). But PHP's method syntax $at->sitemap() looks for an actual sitemap() method on the AgentTools class, which doesn't exist.

    The correct eval call requires chaining the property access with the method call:

    // Works:
    wire('at')->sitemap->generate();
    
    // Fails — treats sitemap as a method call:
    wire('at')->sitemap()->generate();
    

    Why this matters

    AI agents frequently use --at-eval for quick API calls. The sitemap is documented as a first-step orientation tool, so agents will naturally try to call it from eval. Without a clear API path, they hit the error and then see the full help output (which confusingly lists --at-sitemap-generate as a CLI flag, not an API method).

    Suggested fix

    Either (or both):

    1. Add a sitemap() method to AgentTools that returns the helper instance — this makes wire('at')->sitemap()->generate() work naturally from eval:

      public function sitemap() {
          return $this->getHelper('sitemap');
      }
      
    2. Document the correct eval syntax in agent_cli.md and AGENTS.md — use property access, not method call:

      php index.php --at-eval 'wire("at")->sitemap->generate();'
      

    Option 1 is cleaner since migrations has the same property-only pattern and would benefit from the same treatment.

    Environment

    • AgentTools v2 (ProcessWire module)
    • ProcessWire 3.0.247
    • PHP 8.4, DDEV

    pw-at.sh wrapper does not support sitemap-generate

    Problem

    The wrapper script (.agents/skills/processwire-agenttools/scripts/pw-at.sh) only passes through a fixed set of subcommands:

    eval, eval-b64, stdin, stdin-b64, cli, migrations-apply, migrations-list, migrations-test
    

    Any other command exits with the usage message. This means sitemap-generate cannot be invoked through the wrapper:

    bash .agents/skills/processwire-agenttools/scripts/pw-at.sh sitemap-generate
    # prints usage, exits 1
    

    Agents must fall back to calling ddev exec php index.php --at-sitemap-generate directly, which breaks the "always use the wrapper" convention documented in AGENTS.md.

    Suggested fix

    Add sitemap-generate (and any future helper CLI actions) to the wrapper's case statement. One approach:

    # In the argument validation case:
    sitemap-generate|skills-install)
      [[ $# -eq 0 ]] || { echo "$mode does not accept positional arguments" >&2; exit 1; }
      ;;
    
    # In the execution case:
    sitemap-generate)
      run_php "--at-sitemap-generate"
      ;;
    skills-install)
      run_php "--at-skills-install"
      ;;
    

    Or make the wrapper generic: pass any unrecognized subcommand through as --at-<subcommand> to let AgentTools handle validation server-side.

     

    • Like 2
  15. 52 minutes ago, ryan said:

    and install to "/.agents/..."

    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.

  16. 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";'

     

    • Like 2
×
×
  • Create New...