Say which build is answering, on the opening line The session named its lane, its endpoint and its ACP agents but not itself, so there was no way to tell from the screen which build was running -- which mattered the moment a shell function shadowed the installed binary and a stale build answered while looking identical. It reads `coder 0.0.2 · …` now, from `openagents_cli::VERSION`, so it reports the version it was published under rather than the crate manifest's. Both greeting sites, because there are two: the token that was already stored, and the one a login has just produced.
Say which build is answering, on the opening line
Deploy story
What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.
Not deployed through the forge lane
No push, promotion, build, or deploy receipt references this commit (receipts are scanned over a bounded recent window). Changes shipped by full node replacement carry their proof in the release gate receipt instead.
Changed files
-
modified
crates/coder-lite/src/interactive.rs
Diff
1 file changed, +4 -2
crates/coder-lite/src/interactive.rs modified +4 -2
@@ -107,7 +107,8 @@ pub async fn run_tui(options: SessionOptions) -> Result<(), Box<dyn std::error::
| 107 | 107 |
|
| 108 | 108 |
|
| 109 | 109 |
|
| 110 |
|
|
| 110 |
|
|
| 111 |
|
|
| 111 | 112 |
|
| 112 | 113 |
|
| 113 | 114 |
|
@@ -205,7 +206,8 @@ pub async fn run_tui(options: SessionOptions) -> Result<(), Box<dyn std::error::
| 205 | 206 |
|
| 206 | 207 |
|
| 207 | 208 |
|
| 208 |
|
|
| 209 |
|
|
| 210 |
|
|
| 209 | 211 |
|
| 210 | 212 |
|
| 211 | 213 |
|