Hi guys, gentlemen and other binaries, hexanal, decimal and other TW5 fans!
Jumped here from TW Google Group, some long time was away from lovely TW5 :)

Well my idea it a very simple idea - turning TW5 into an LLM agent. Cuz all these so called LLM Agents are JSON array messages hanglers and no more.

What do you thing of this idea? Could be such tool will will spark big interest in TW5 :)

So I am starting with that simple proxy where I am going to push REST directly from TW5 tiddler aiming to http://localhost:3000/api/

For example http://localhost:3000/api/models

// deno run --allow-net --cert C:\certs\mycorpsert-ca.pem native_proxy.ts

// native_proxy.ts
import { serve } from "https://deno.land/std@0.200.0/http/server.ts";

const TARGET = "https://gateway-ai.mycorp.com";
const PORT = 3000;

serve(
  async (req) => {
    const url = new URL(req.url);

    // do route just for /api/*
    if (url.pathname.startsWith("/api")) {
      const targetUrl = TARGET + url.pathname.replace("/api", "") + url.search;

      // Clone headers, delete host
      const headers = new Headers(req.headers);
      headers.delete("host");

      try {
        const response = await fetch(targetUrl, {
          method: req.method,
          headers,
          body: req.body,
        });

        // response handle
        return new Response(response.body, {
          status: response.status,
          statusText: response.statusText,
          headers: response.headers,
        });
      } catch (error) {
        return new Response(`Proxy error: ${error.message}`, { status: 502 });
      }
    }

    return new Response("Not found", { status: 404 });
  },
  { port: PORT },
);

console.log(`Proxy listening on http://localhost:${PORT}`);

Then I started to google existing JSON handling plugins for TW5 and https://joshuafontany.github.io/TW5-JsonMangler/ from Joshua Fontany looks promising. But,
I stumbled upon a JSON kind of error in vanilla TW5 but found out that this is a feature not an error :)

<$transclude tiddler=myJsonTiddler index=myindex /> works perfectly in TW5-JsonMangler
and doesn't work in vanilla TW5 5.3.8
because $tw.wiki.extractTiddlerDataItem happened to be a bit patched by Joshua

described all it here #3075

So my second question - is it a usual and normal way to create a TW5 fork with patching modules like $wiki.js and so on ?
I mean it could be good to save compatibility with future TW5 versions 🤔🤷‍♂️

And could you please advice what me better to do if I need TW5-JsonMangler (it's seems dated by 2018) behavior but want to be alined with 5.3.8 and future vanilla TW5 ?

Thank you!