Question 1

How is the input parsed?

Accepted Answer

The dialect (indented text, path list, JSON, YAML, Markdown nested list) is auto-detected by scoring each parser's confidence and picking the winner. The dialect chips let you override the auto-detect.

Question 2

What is the path-list input mode?

Accepted Answer

Paste output from find, git ls-files, aws s3 ls --recursive, or any list of slash-separated paths. Treekit splits on / or \, dedupes intermediate directories, and reconstructs the tree without you re-indenting.

Question 3

How does the annotation column work?

Accepted Answer

Each node can carry a trailing annotation (the ← project-wide overview pattern). The annotation column is auto-aligned to a single column at the requested total width budget.

Question 4

Which output formats are supported?

Accepted Answer

Eleven dialects: Unicode tree, ASCII tree, Markdown nested list, YAML, JSON, Mermaid graph, Graphviz dot, semantic HTML <ul>, org-mode outline, paths list (one per line), and a mkdir -p shell script that recreates the tree.