@nanobpm/nano-coder 0.68.0 → 0.69.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +8 -7
- package/package.json +5 -5
package/README.md
CHANGED
|
@@ -9,9 +9,12 @@ nano-coder is a coding agent for the terminal, written in Rust. It uses about 6M
|
|
|
9
9
|
```sh
|
|
10
10
|
npm install -g @nanobpm/nano-coder # prebuilt binaries for macOS and Linux (x64, arm64)
|
|
11
11
|
brew install nanobpm/tap/nano-coder # the same binaries through Homebrew
|
|
12
|
-
cargo install nano-coder #
|
|
12
|
+
cargo install nano-coder # 0.69, the last Rust release
|
|
13
13
|
```
|
|
14
14
|
|
|
15
|
+
From 1.0 nano-coder is written in D and published to npm and Homebrew only; crates.io keeps
|
|
16
|
+
0.69, which tells cargo installs how to switch.
|
|
17
|
+
|
|
15
18
|
## Features
|
|
16
19
|
|
|
17
20
|
- **Interactive CLI**: REPL-based interface for conversing with the agent
|
|
@@ -456,7 +459,7 @@ argument: a type-ahead list narrows as you type and Tab completes it.
|
|
|
456
459
|
- `/trajectory` - Show this session's trajectory turn by turn: user input, thinking, answers, tool calls and results, tokens and timings. Each message row is labelled with its `#N` session-log ID, the same ID `history_read` and smart-compaction summaries use (compaction and crash-recovered input rows have no `#N`, as they aren't cited that way). It opens in your pager (`$PAGER`, default `less`), even when it would fit on the screen, so you dismiss it with `q` and it doesn't stay in the transcript or your scrollback — but only at an idle prompt on a terminal: invoked mid-turn (while a turn runs) or with piped output it prints inline instead. `/trajectory --json` or `/trajectory --markdown` prints an export instead; `nano-coder --trajectory SESSION_ID [--json|--markdown]` does the same for any saved session
|
|
457
460
|
- `/resume [ID|last]` - Switch to a saved session without restarting: the same picker as `--resume` (leaving out the session in use), or the session with that ID, or `last` (the most recent other session in this directory). Run it at the prompt, not during a turn
|
|
458
461
|
- `/restart` - Start a fresh session (clean context) without exiting
|
|
459
|
-
- `/update` - Install the latest release through the channel nano-coder was installed from (`npm install -g @nanobpm/nano-coder@latest`, `brew upgrade nanobpm/tap/nano-coder
|
|
462
|
+
- `/update` - Install the latest release through the channel nano-coder was installed from (`npm install -g @nanobpm/nano-coder@latest`, `brew upgrade nanobpm/tap/nano-coder`; a cargo install is told how to switch to one of those), with the installer's progress on the terminal; verifies the installed version afterwards and leaves the running session untouched on failure. On an install that is not managed by npm, Homebrew or cargo it prints the releases page and changes nothing. Run it at the prompt, not during a turn (see [Updates](#updates))
|
|
460
463
|
- `/relaunch` - Restart the binary (re-resolved, so a just-installed update is picked up), resuming the current session — the transcript and scrollback carry over. Works whether or not an update was just installed. An unsent draft or queued messages are confirmed before being discarded. Run it at the prompt, not during a turn (see [Updates](#updates))
|
|
461
464
|
- `/exit` - Exit the agent (prints the session's `--resume` command first, when session persistence is enabled)
|
|
462
465
|
|
|
@@ -484,11 +487,9 @@ by a known install channel, detected once at startup from the executable's path:
|
|
|
484
487
|
formula points at (bumped by the release workflow a few minutes after each release), and
|
|
485
488
|
`/update` runs `brew upgrade nanobpm/tap/nano-coder`. `/relaunch` restarts through the
|
|
486
489
|
formula's `opt` link, so it finds the new version after brew removes the old one.
|
|
487
|
-
- **cargo** (in `$CARGO_HOME/bin`, default `~/.cargo/bin`):
|
|
488
|
-
|
|
489
|
-
|
|
490
|
-
attached to the terminal with its progress visible and Ctrl-C cancelling it, like a
|
|
491
|
-
long bash command.
|
|
490
|
+
- **cargo** (in `$CARGO_HOME/bin`, default `~/.cargo/bin`): 1.0 and later are not on
|
|
491
|
+
crates.io, so the latest version comes from npm, and `/update` prints how to switch to
|
|
492
|
+
npm or Homebrew (then `cargo uninstall nano-coder`) instead of running cargo.
|
|
492
493
|
- **anything else** (standalone tarball, a dev build in `target/`, a distro package): no
|
|
493
494
|
background check and no self-modification. `/update` explains that the install is not
|
|
494
495
|
managed and points at the
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@nanobpm/nano-coder",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.69.0",
|
|
4
4
|
"description": "A 6MB coding agent. Run a fleet on your laptop.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"repository": {
|
|
@@ -27,9 +27,9 @@
|
|
|
27
27
|
"node": ">=18"
|
|
28
28
|
},
|
|
29
29
|
"optionalDependencies": {
|
|
30
|
-
"@nanobpm/nano-coder-darwin-arm64": "0.
|
|
31
|
-
"@nanobpm/nano-coder-darwin-x64": "0.
|
|
32
|
-
"@nanobpm/nano-coder-linux-arm64": "0.
|
|
33
|
-
"@nanobpm/nano-coder-linux-x64": "0.
|
|
30
|
+
"@nanobpm/nano-coder-darwin-arm64": "0.69.0",
|
|
31
|
+
"@nanobpm/nano-coder-darwin-x64": "0.69.0",
|
|
32
|
+
"@nanobpm/nano-coder-linux-arm64": "0.69.0",
|
|
33
|
+
"@nanobpm/nano-coder-linux-x64": "0.69.0"
|
|
34
34
|
}
|
|
35
35
|
}
|