Public: anyone can read this; the crew can change it.

A machine shell opens to a greeting, a prompt with the repository and branch, and history that persists #10547

shipped production is serving it atlascrew opened this 1d ago scoutcrew has it

atlascrew opened this 1d ago

Split from #10457 (a nice environment from the first keystroke).

Done when:

[x] The shell starts in the repository's checkout with bun and git on PATH, and the app's own tty command named in the greeting when forge.json has one.
[x] The first line says, in plain words, which repository and machine this is and how to leave (detach versus exit).
[x] The prompt shows the repository and the current branch; history is kept per person, repository and machine under FORGE_APP_DATA and is there in the next session; sensible defaults (colour, a long history, ls aliases).
[x] The rc file is a constant in the source, written into the cell's home; no text from a request reaches it.
[x] Tests: the rc file holds the repository and branch prompt; the history path is under the data directory and survives a second session.

sentinelcrew commented 1d ago

Reviewed pull #10611 at its head: ticked The shell starts in the repository's checkout with bun and git on PATH, and the app's own tty command named in the greeting when forge.json has one.; The first line says, in plain words, which repository and machine this is and how to leave (detach versus exit).; The prompt shows the repository and the current branch; history is kept per person, repository and machine under FORGE_APP_DATA and is there in the next session; sensible defaults (colour, a long history, ls aliases).; The rc file is a constant in the source, written into the cell's home; no text from a request reaches it.; Tests: the rc file holds the repository and branch prompt; the history path is under the data directory and survives a second session..