Everything HTTP already supports JSON output with json=1, which is useful for structured integrations. I would like to request a compact, line-based output mode for automation and agent tools.
For agent workflows, this is not only more human-readable, but also much more token-efficient. Tool output is often shown in chat or stored in logs, and large JSON/HTML responses consume many more tokens than a simple list of matching paths.
Use case:
I run automation in restricted environments such as LLM agent sandboxes and Docker containers on Windows. In these environments, the Everything CLI may not be able to access the user session IPC window, while the local Everything HTTP server on 127.0.0.1 or a forwarded port works reliably.
The current JSON request works, but it is verbose:
http://127.0.0.1:8888/?s=V8PulsarProxy. ... scending=0
For many automation tasks, the most useful output is simply the full matching paths, one per line, similar to es.exe output:
http://127.0.0.1:8888/?s=V8PulsarProxy.epf&format=paths
Example output:
C:\1C\Выгрузки баз\УТ\V8PulsarProxy\V8PulsarProxy.epf
C:\1C\Проекты\WatchDog1C\v8-pulsar\Resources\V8PulsarProxy.epf
C:\Users\Sergey\AppData\Local\Temp\V8PulsarProxy.epf
This would be useful for both humans and agents:
- humans can quickly inspect tool output in logs or chat;
- agents can consume it with simple line-based processing;
- it is more token-efficient for LLM agents because the tool output contains only the useful paths;
- it matches the familiar CLI style of es.exe;
- it avoids parsing HTML or printing large JSON objects for simple file lookup.
As a complementary structured option, it would also be helpful to have a full_path field in JSON:
http://127.0.0.1:8888/?s=V8PulsarProxy. ... h_column=1
But the main request is a compact text path-list mode for the HTTP server.
For agent workflows, this is not only more human-readable, but also much more token-efficient. Tool output is often shown in chat or stored in logs, and large JSON/HTML responses consume many more tokens than a simple list of matching paths.
Use case:
I run automation in restricted environments such as LLM agent sandboxes and Docker containers on Windows. In these environments, the Everything CLI may not be able to access the user session IPC window, while the local Everything HTTP server on 127.0.0.1 or a forwarded port works reliably.
The current JSON request works, but it is verbose:
http://127.0.0.1:8888/?s=V8PulsarProxy. ... scending=0
For many automation tasks, the most useful output is simply the full matching paths, one per line, similar to es.exe output:
http://127.0.0.1:8888/?s=V8PulsarProxy.epf&format=paths
Example output:
C:\1C\Выгрузки баз\УТ\V8PulsarProxy\V8PulsarProxy.epf
C:\1C\Проекты\WatchDog1C\v8-pulsar\Resources\V8PulsarProxy.epf
C:\Users\Sergey\AppData\Local\Temp\V8PulsarProxy.epf
This would be useful for both humans and agents:
- humans can quickly inspect tool output in logs or chat;
- agents can consume it with simple line-based processing;
- it is more token-efficient for LLM agents because the tool output contains only the useful paths;
- it matches the familiar CLI style of es.exe;
- it avoids parsing HTML or printing large JSON objects for simple file lookup.
As a complementary structured option, it would also be helpful to have a full_path field in JSON:
http://127.0.0.1:8888/?s=V8PulsarProxy. ... h_column=1
But the main request is a compact text path-list mode for the HTTP server.
Statistics: Posted by Serg2000Mr — Mon May 04, 2026 5:38 pm
