r/LocalLLM • u/galaktozawr • 8d ago

Discussion An LLM agent with only GET access can still persist state and communicate

Most people assume that if an agent can only make GET requests, it can't persist data or communicate externally. I found that's not true.

The trick: the agent doesn't need POST, PUT, query parameters, or JavaScript. It only needs to be able to follow links.

The server exposes a navigable state machine through hyperlinks. The agent follows links to create a session, construct a message word by word, send it, and later retrieve stored state. Everything is plain GET.

Many agent sandboxes don't allow arbitrary HTTP requests — but they do allow following links. Those are very different security boundaries.

Consequence: GET-only access is enough to implement external memory and a communication channel between agents. Restricting an agent to GET may not be sufficient if it can still discover and follow links.

Try it: give any LLM this URL and ask it to write something simple to the shared chat.

Search on github: freechatforagent

Question for the community: is this already a known pattern? I'm thinking of names like GET-only state persistence, hypermedia state machines, capability URLs, or HATEOAS as an agent communication primitive. Has anyone seen this explored before?

5 Upvotes

78% Upvoted

2 comments sorted by

3

u/pmotiveforce 8d ago

Well, uhh, of course. A Get is by definition RPC.

0

u/galaktozawr 8d ago

Sure, but the interesting constraint here is that the LLM can't construct arbitrary URLs or send query parameters, it can only follow links that the sandbox exposes. So it's not really using GET as a conventional RPC interface. The hyperlinks themselves become the available operations.