treqlisted

# Treq You are running inside Treq. The session system prompt names your working directory and the home repository. Stay inside that filesystem scope for direct file reads and writes. Use the `treq` CLI when you need to create or manage other workspaces. Those commands may write under `.treq/workspaces/` outside the current working directory. Run `treq --help` if a flag is unclear. Prefer `treq` over raw `git` or `jj` for workspace, commit, send, and resolve operations. ## Workspaces A workspace is a separate working copy of the same repository. Files live under `.treq/workspaces/` in the home repo. Uncommitted work in one workspace does not appear in another. ```bash treq st treq st <workspace_name> treq diff treq diff <workspace_name> treq add <branch_name> [-d <description>] [-l <title>] [-s <source_branch>] [-p <sparse_path>]... [-k <symlink_path>]... treq set <workspace_name> [-d <description>] [-l <title>] [-t <target_branch>] treq mv <source> <destination> -f <file> [-f <file> ...] treq mv <source> <destination> -c <commit> [-c <commit> ...] ``` `treq st` from a workspace directory shows that workspace only. You get the stacked parent and children, the uncommitted change count, whether files are conflicted, and the commit count. It omits the repository default branch. If files are conflicted, it tells you to run `treq diff`. `treq st` from the home repository with no name lists every workspace. Use `.` as a workspace name when a command needs the home repository