<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pardes.git/test/process/cli.zig, branch main</title>
<subtitle>Pardes</subtitle>
<id>https://git.0x4200.cafe/pardes.git/atom?h=main</id>
<link rel='self' href='https://git.0x4200.cafe/pardes.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.0x4200.cafe/pardes.git/'/>
<updated>2026-11-17T15:15:01Z</updated>
<entry>
<title>main: the command line is commands that describe themselves, over the tree that does</title>
<updated>2026-11-17T15:15:01Z</updated>
<author>
<name>Gabriel Schneider</name>
<email>gbrls@0x4200.cafe</email>
</author>
<published>2026-11-17T04:15:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0x4200.cafe/pardes.git/commit/?id=2e6777e06e3f3e9d59ec847b98e0cb676d04296a'/>
<id>urn:sha1:2e6777e06e3f3e9d59ec847b98e0cb676d04296a</id>
<content type='text'>
The user: "the cli should be like a living documentation, similar to 9p
and maybe even share the source code but with different sinks", rex's
CLI the model. pardes [flags] [FILE] opens, starts or pages as it did; a
first word naming a command is that command (a file named so is ./ps, or
after --): ps, attach [NAME], kill NAME|--all, new [flags] [FILE] for
sessions; do WORD [ARG] and words [GROUP] for the builtins; fs VERB [PATH]
for the tree; help [CMD|WORD|PATH], completion SHELL, skill, version.

One definition, several sinks. main.zig's `cmds` (an EnumArray over the
Cmd enum: group, args, first-screen line, doc, examples, see-also) is
both what args[1] is matched against and every command's help; `flags`
(over the Flag enum: what it takes, its doc, session/open/old) is both
the flag loop's parser and `help new`. The 70-line help_text and the flag
enum kept apart from it are gone; every flag behaves as before, and
--ps, --attach[=NAME], --kill=NAME, --kill-all, -h/--help and --version
are the commands' old spellings for a release (EDITOR='pardes --wait'
unchanged). What a word or a file does is the tree's to say: words,
help WORD, help PATH, fs and the completions read /commands and /README
over cloud9's Fsys, from the session (-s NAME, else $PARDES_9P, else the
only one whose socket answers) or, with none, from a core this process
makes (Pardes.create, never stepped: no shell, file or socket) and serves
on one end of a socket pair to an Fsys on the other (`Here`: cloud9's
engine, one thread), so both are the same client over the same tree.
With no session, fs ls/stat/help/complete and a read of README, commands
or ctl answer; a read of anything else, or a write, says it is a running
session's and how to start one. do picks the ctl by /commands' scope (a
pane's word needs $PARDES_PANE or -p N) and prints a refusal in the
session's words. completion prints a bash, fish or zsh script that asks
`pardes completion -- WORDS` back. skill prints src/skill.txt, the
recipes and traps, which leaves the inventory to pardes help. version
adds the 9P the tree speaks.

The reference's "The pardes command" includes docs/typ/command-line.txt,
`pardes help --all` (never a session's), which the builtins-json step
(-Dplatform=tui) now writes too; a main.zig test fails when it is stale.
test/process/cli.zig: five cases through the binary, with and without a
session; flags' eight pass unchanged.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
Claude-Session: https://claude.ai/code/session_016Y9MNBECMWcJD5pdS4SR6T
</content>
</entry>
</feed>
