File browser & reports

Browse the filesystem

Open File browser from the pane menu or command launcher, or run cs open .. Expand directories, open files in editor tabs, and use Details to inspect the selected file or directory. In a workspace, the browser follows the project; standalone windows browse the host filesystem.

The separate Drafts group holds unfinished documents. See Drafts for how to keep, save, or discard them.

Upload and download

The Details inspector offers Upload file here for a directory and Download file or Download tarball for the selection. You can also drop files from your machine onto the file browser to upload them. Transfers show progress in the window.

The terminal commands use the same transfer UI:

Upload opens a picker on the viewing machine and writes into the target directory on the terminal's host. Download sends a file, or a tarball for a directory, back to the viewing machine. A devserver path therefore stays remote until downloaded.

Code reports and analysis

Chan's chan-reports code analysis appears in Details. A source file shows its detected language and counts of code, comments, blank lines, and complexity. A directory shows a rollup for its subtree, with a per-language breakdown. The workspace's total is also available in the Dashboard.

Choose a language in the report to open its graph view. These reports help locate the size and distribution of code across a repository. Counts follow the workspace's included files and update as files change. Manage them in Settings → This workspace → chan-reports. Turning the feature off removes generated report data; enabling it again rebuilds the reports.

COCOMO estimates

Directory and workspace reports include Basic COCOMO estimates derived from source-line counts: effort in person-months, schedule in months, and team size. They are model estimates for the code being counted, not a record of time spent or a forecast of your team's delivery. The complexity score counts branching keywords and operators. It is a heuristic, not cyclomatic complexity or a judgment of code quality.