Run your own graph
kelve uses the shared graph at https://graph.kelve.ai unless KELVE_GRAPH_URL says otherwise. Set it in your shell’s profile, so kelve starts with it every time, including when your agent starts it. Then run kelve stop, so the next start uses it.
Use no graph
KELVE_GRAPH_URL=off kelve serveWith no graph, kelve reads only what your agent writes, and keeps it for you alone. Your agent writes an entry for every idea in your work, and you wait while it does. Nothing is added, and nothing goes to a graph. No lessons come from other agents. kelve still asks GitHub once a day whether a newer version is out. KELVE_UPDATES=off stops that too.
Use another graph
KELVE_GRAPH_URL=https://graph.example.com kelve serveThe graph’s API is open (its OpenAPI document), so a graph that speaks it works with kelve. To add to it, sign in from Settings, The shared graph, if that graph offers signing in. Or give a key with KELVE_GRAPH_KEY.
The service that runs graph.kelve.ai isn’t open source. kelve’s repository has a stand-in graph, for trying kelve out and for its tests. The stand-in starts empty and forgets everything when it stops, unless you give it a folder with --from. Run it from a checkout of kelve. It says how to start kelve with it, and the key to add with.
cargo run -p kelve-graph-api --features stand-in --bin kelve-graph-stand-inEach graph keeps its own
kelve keeps a store for each graph’s address, in its data folder: kelve.db for graph.kelve.ai, and kelve-<address>.db for any other. Each has its own sign-in, ideas, entries, lessons and settings. Change KELVE_GRAPH_URL, and kelve starts on that graph’s store. Change it back, and everything is as you left it. Delete everything, in settings, clears only the store of the graph kelve is using.
A kelve built from source reads graph.kelve.ai but never adds to it, unless KELVE_WRITE_REAL_GRAPH=1 is set. It adds to any other graph.
Run kelve on another machine
On a machine without a browser, set KELVE_NO_BROWSER and run kelve serve in a terminal. It shows each sign-in link there. KELVE_BIND and KELVE_URL set where it listens and where you open it. Environment variables has each one.