l0ng-ai d601a86f11 docs(cli): the environment comes from the server too ...

Same shape as the working directory, and the same surprise:

    RALPH_MARKER=hello tty7 run -- sh -c 'echo [$RALPH_MARKER]'
    []

The pane is the server's child, so it gets the server's environment.
`FOO=bar tty7 run -- …` is a universal idiom and it silently does
nothing here, with no `--env` to reach for instead.

Documented beside the `--cwd` note, with the workaround that does work
— set the variable inside the command, where the shell running it can
see it. Adding `--env` would be a new flag, not a fix.

Checked while here, and correct: a pane does get a usable environment
(PATH, HOME) from the server; `$TTY7_PANE`, `$TTY7_WS` and
`$TTY7_CONFIG_DIR` are all set in a `run` pane as the top-level help
promises; and the payoff holds — `tty7 procs` with no address, run
inside a pane, resolves `$TTY7_PANE` and reports that pane's own
processes.

2026-08-16 08:03:46 +08:00

..

src

docs(cli): the environment comes from the server too

2026-08-16 08:03:46 +08:00

tests

test(e2e): pin the tree and the registry agreeing under a race

2026-08-16 07:55:15 +08:00

Cargo.toml

fix(cli): submit send enter outside paste bursts (#322)

2026-08-03 16:55:48 +08:00