Question 1

Does Jeview change my answers, or is it a pure pass-through?

Accepted Answer

Pure pass-through. It is a gateway that sits between your code and TypeSafe and answers nothing itself: it forwards each request to Jev with your key, hands the answer back, drops its own headers before calling, and sends the body on unchanged. Point a client at http://127.0.0.1:4777/v1/systemone instead of the real endpoint and the requests and answers are the same.

Question 2

Is it safe to leave running on a shared or remote machine?

Accepted Answer

Treat it as single-user local only. It listens on 127.0.0.1 and has no login, so anything running on your machine can read the recorded calls and send calls with your key, and the README says explicitly not to put it behind a public address. It does refuse requests from pages on other sites, so a site you visit cannot drive it.

Question 3

Where does my API key live, and how do I wipe everything?

Accepted Answer

Calls and the key go into jeview.sqlite in the data folder, readable only by you, with the key stored as plain text. Nothing is stored anywhere else: there are no accounts and no tracking, and the only place it sends anything is TypeSafe, to make the calls you asked for. To erase everything including the key, stop Jeview and delete jeview.sqlite* from that folder.

Question 4

Will a long-running history get slow or expensive?

Accepted Answer

A long history stays cheap on disk and in the viewer: it opens on the latest 20,000 calls and search reaches the rest. The only things making live calls are the two demos, which send real requests while their page is open, cost about ten cents an hour while playing, and stop with Ctrl-C. Group calls by adding a path prefix, and chain them with the Jeview-Trigger header so the map grows one request off an earlier answer.

Question 5

How do I run it, and is there anything to install first?

Accepted Answer

Node 24 or later is the whole requirement; Jeview has no dependencies to install. Run ./launch.sh, which finds a suitable Node on your PATH or installed by nvm or Homebrew, starts the gateway and opens the viewer, or npm start to do the same without opening a browser. A running instance also serves its own llms.txt describing its address and whether a key is set.

Question 6

Can I change the port, the database folder, or the endpoint it calls?

Accepted Answer

Both launchers accept --port, default 4777, --dir such as ~/.local/share/jeview for where the database lives, and --jev-endpoint URL to forward somewhere else, such as a local mock. Two Jeviews can share one data folder, for instance on two ports, and each shows the calls of both.

Question 7

The map labels answers with keys like c14. Can it show names instead?

Accepted Answer

Yes, with the Jeview-Display header. Point it at the part of an option's criteria to render, either one field or one per question, as in category=name, kind=title. An option without that field keeps its key, and anything sent without the header is unchanged. The header is cosmetic: one that cannot be read is ignored, never refused.

Jeview · andududu

About this project

Highlights

Quickstart

Questions about this entry

Other listings of this project

From the Jev guides

From the Jev AI model community