nimbus-cli works either way round. Give it a subcommand and it runs that one command
and exits; give it nothing and it opens a REPL. Both drive the same session file, so
the vault you selected and the directory you were in survive between invocations.
# one command per invocation
$ nimbus-cli new vault.toml
(registers a vault from vault.toml; see README.md for the config format)
$ nimbus-cli cd my-vault/docs
$ nimbus-cli ls
(lists my-vault:/docs — the previous `cd` is what put us there)
# or the REPL, for a bare invocation
$ cargo run -p nimbus-cli
nimbus />> vaults
(prints registered vault names)
nimbus />> select my-vault
nimbus my-vault/>> ls
(lists my-vault's current directory)
nimbus my-vault/>> cd docs
nimbus my-vault/docs>> put notes.txt
(copies notes.txt out of the local vault into my-vault:/docs)
nimbus my-vault/docs>> get notes.txt my-vault downloads
(copies my-vault:/docs/notes.txt into the local vault's downloads/ — the arguments
are positional, so naming the source vault is what lets you name a destination;
with neither, `get notes.txt` lands it in the local vault's root)
nimbus my-vault/docs>> exit
(saves the session and quits; Ctrl-C/Ctrl-D do the same)
To run several commands in one process, pipe them into the REPL:
printf 'select my-vault\nls\n' | nimbus-cli
See README.md for the full command reference.