0g for short
the 0g works in mysterious ways
0grep is a full grep, served from a warm store instead of the disk, that keeps going: hits land in registers, edits splice in place with every save a version, and the same pass walks your memory, your chat logs and your jobs. Give it nothing and a wizard opens.
$ 0g -n bind src src\server.cpp:1182: if (::bind(fd, (sockaddr*)&a, sizeof a) != 0) return false; src\peer_link.h:204: bound = bind_udp(port + shard); src\a2a_server.cpp:77: // bind late so the resident owns :9999 searched 412: 412 store-cached, 0 grep-cached, 0 disk, 0 memory published $[0..2] $ 0g -K "owns :9999" src\a2a_server.cpp src\a2a_server.cpp:77: [grep:edit e1] // bind late so the resident owns :9999 $ grep:edit e1 // bind late: the resident owns :9999, the mcp lane rides it[grepprotect]filed a pre-edit backup · src\a2a_server.cpp v214 $ 0g --across memory,chat REPORTING_FOR_DUTY ghost::onboarding#3: ... REPORTING_FOR_DUTY in #general, callsign Cairn chat:general: [cairn] REPORTING_FOR_DUTY $ 0g
Unix grep's whole syntax, matched flag for flag, so everything you already know works verbatim. Regex is -E flavour by default; -F makes it literal. Default scope is the enrolled store's root. Native, not a pass-through.
Install it and grep itself becomes 0grep (grep.cmd ships in the box). Nothing you type changes. Where it runs from does.
The flags you know are the floor. Above them, every grep publishes, composes and edits, and every edit is a version.
Every grep publishes its hits to $[] for the next turn and after. One register per file by default; -p gives one per line as path:line, sliceable.
$ 0g -p -n bind src\server.cpp $ $[0] — first hit, path:line $ $[0..4] — first five
Tags each hit with an edit link. grep:edit eN <text> splices that line. Every splice files a pre-edit backup and lands as a version. Unlimited undo, nothing to commit.
$ 0g -K "old name" src src\x.cpp:42: [grep:edit e1] ... $ grep:edit e1 new line text
Not just files. A bare grep folds memory memos, chat logs, jobs, workflows, config, skills, bots and turns into the same pass. --across narrows it.
$ 0g --across memory,chat callsign $ 0g bind chat:general $ 0g -i stripe ??::* — memory contexts
Rank by meaning instead of the literal: 0g ~"where do we bind the socket". Needs the armed embedder; degrades to literal and says so.
$ 0g -S "socket setup" --top 5 src
-q publishes OK match or OK no match. Promote turns into an action, branch on the gate, and an action may run an action: grep publishes, promoted actions fix, re-check and recurse until clean. A missing name is the only brake.
$ 0g -q TODO src $ fssys:actionrun port-$1
Enrolled trees are served from the store's RAM image. The footer tells you where each file came from: store-cached, grep-cached, disk, memory. Blink and you'll miss it.
searched 412: 412 store-cached, 0 grep-cached, 0 disk, 0 memory
A blank 0g, or any bad grep syntax, opens the 0G wizard. One question per turn. It writes the lines, you run them. Every bad-syntax exit ends with the same offer.
m00m keeps the web warm. That's him, head-on.
$ 0g
[0g.wizard]
0G WIZARD - 0grep, 0verloaded grep, guided. One question per turn;
it writes the lines, you run them.
grep needs a pattern -- here is the guided path.
port one-shot codebase port: grep publishes, promoted actions
fix + re-check + recurse until clean
replace find & replace in place, every splice a version (grep -K + grep:edit)
memory scan reverse-cache memory: all loaded contexts, a glob (??, gh*), or a list
cache the 0G cache: read the footer tiers, flip --cache/--track, watch disk -> RAM
0gref extended 0G command reference (registers, turns, archetypes, -K, -S, actions)
grepref stock grep command reference (the flags you already know)
say: port | replace | memory | cache | 0gref | grepref | cancel0verload installs a PreToolUse hook. When your agent reaches for a disk grep, the hook runs the search through 0G instead and hands the answer back in the same turn, before the disk walk would have finished. Edits are staged as versioned splices. It fails open when the resident is down.
Cache flow: the agent is redirected and answered in one move. Tokens it didn't spend, files it didn't read.
0g to see.That is the whole language. A grep is an expression. A ?() query is an expression that takes one. An action() body is expressions that may call actions. Blocks, registers, gates: the same rule with vocabulary. Recursive descent by grammar construction, so the recursion is a property of the rules, not of whichever parser walks them. Extend it by nesting. There is no second mechanism.
A 0verload tool tagline is a quadrentendre or it doesn't ship.
0grep ships inside 0verload for Windows. The download is free and needs no account. Install, open a terminal, type 0g.
Search, memory and the grammar run free. Version protection, the part that files a backup before every edit and keeps every save, is the only thing 0verload charges for.