TazPod CLI Reference

Runtime: TazPod Architecture
Vault: TazPod Vault Security
Recovery: TazPod Nomadic Workflow
Hub: TazPod Entity

This page maps the real command surface of tazpod from cmd/tazpod/main.go and the command implementations in cmd/tazpod/.

Primary Dispatch Table

Command	Real Target	Notes
`tazpod`	`smartEntry()`	default no-args path
`tazpod init`	`initProject()`	creates `.tazpod/`, `.tazpod/vault/`, and config
`tazpod up`	`up()`	ensures container is running and starts sync daemon
`tazpod down`	`down()`	stops and removes container
`tazpod ssh`	`enter()`	alias of `enter`
`tazpod enter`	`enter()`	interactive shell path
`tazpod unlock`	`unlock()`	decrypt vault into RAM and bridge AWS
`tazpod lock`	`lock()`	unmount RAM enclave and AWS bind mount
`tazpod save`	`save()`	re-encrypt RAM vault back to disk
`tazpod pull vault`	`pullVault()`	S3 -> local encrypted vault
`tazpod push vault`	`pushVault()`	local encrypted vault -> S3
`tazpod sync`	`pull()` dispatcher	currently handled by the same dispatcher family as `pull`; operationally worth remembering
`tazpod login`	`login()`	runs `aws sso login --profile <profile>`
`tazpod vpn`	`vpnCommand()`	legacy / untrusted path
`tazpod setup-storage`	`setupStorage()`	bucket creation helper for `tazlab-storage`
`tazpod __internal_sync_daemon`	`syncDaemon()`	internal background daemon
`tazpod __internal_env`	`printExportEnv()`	internal shell helper; currently placeholder

Use this as the normal path. It already includes smart recovery logic:

Use this if you want the container and sync daemon running without immediately entering an interactive shell.

Use this on a fresh machine or when .tazpod/vault/vault.tar.aes is missing locally.

Use this when you want an explicit S3 sync instead of waiting for the daemon cycle.

From .tazpod/config.yaml and cmd/tazpod/config.go: