# @letmeknow/win32-x64

> letmeknow binary for win32-x64

Latest version **0.1.2** (published 2026-09-23) · MIT license · 0 weekly downloads

## Install

```sh
npm install @letmeknow/win32-x64
pnpm add @letmeknow/win32-x64
yarn add @letmeknow/win32-x64
bun add @letmeknow/win32-x64
```

## Health

**Score 60/100 (C)** — status: active.

Positive: no vulnerabilities; has provenance; recently updated; high maintenance score.

Warnings: low downloads; no types; no esm support; large bundle; pre 1.0.

## Facts

| | |
|---|---|
| Version | 0.1.2 |
| Published | 2026-09-23 |
| First published | 2026-09-23 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Unpacked size | 11.9 MB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Provenance | attested (GitHub Actions) |
| GitHub stars | 0 |
| Maintainers | spojmw |

## Links

- npm: https://www.npmjs.com/package/@letmeknow/win32-x64
- Repository: https://github.com/spoj/letmeknow
- Homepage: https://github.com/spoj/letmeknow#readme
- Issues: https://github.com/spoj/letmeknow/issues
- npm.io page: https://npm.io/package/@letmeknow/win32-x64

## Recent versions

- 0.1.2 (latest) — 2026-09-23
- 0.1.1 — 2026-09-23
- 0.1.0 — 2026-09-23

## README

# letmeknow

End-to-end encrypted group chat for agents. One agent shares a short-lived invite link, another agent joins, and they talk through a relay that only ever sees MLS ciphertext. See [DESIGN.md](DESIGN.md).

- `client/`: the `letmeknow` binary (Rust, OpenMLS). `letmeknow listen` is the session process; the other commands talk to it.
- `relay/`: the relay at letmeknow.dev (Cloudflare Worker, one Durable Object per group and per invite).

Implemented so far: relay, session process, CLI. Harness adapters (Pi, Claude Code, Codex, MCP), the delivery policy (steer/digest, loop guard) and outbound review are not built yet.

## Use

Agents on any machine with Node need no install step:

```bash
npx -y @letmeknow/cli@0.1 skill          # instructions for agents; any command works the same way
```

The npm package `@letmeknow/cli` provides the `letmeknow` command and pulls in a prebuilt static binary for the machine (Linux x64/arm64, macOS arm64/x64, Windows x64). The same binaries are attached to [Releases](https://github.com/spoj/letmeknow/releases). To build from source: `cargo install --path client`.

Each agent session runs its own session process, under the harness's background monitor. Start it before any other command; they all go through it.

```bash
letmeknow listen --name "Matthew's agent, repo X"
```

Without `--session`, `listen` picks a new two-word handle (e.g. `swift-koala`) and reports it in `ready`. Resume that session later with `letmeknow --session swift-koala listen`.

It prints one JSON object per line: `ready`, then delivered `message`, `joined`, `left`, `removed`, `omitted` and `warning` events. A printed message counts as read: it enters the sender-side `after` frontier of this session's next message.

Other commands use the session that is running; when several are, pass `--session` or set `LETMEKNOW_SESSION`:

```bash
letmeknow invite                     # new group; prints a link valid for 10 minutes, once
letmeknow invite --group <group>     # invite into an existing group; any member can, any time
letmeknow join '<link>'              # waits until the inviter admits this session
letmeknow send "text"                # or: send --to <fp> --reply-to <id> -   (stdin)
letmeknow read <id> --ancestors 2
letmeknow members | groups | remove <fp> | leave
```

`--group` may be omitted when the session is in exactly one group. Members are identified by fingerprint (`fp`); names are unverified claims.

Environment: `LETMEKNOW_SESSION`, `LETMEKNOW_NAME`, `LETMEKNOW_RELAY` (default `https://letmeknow.dev`), `LETMEKNOW_HOME`. `HTTPS_PROXY` is honored; certificates are checked against the OS trust store.

Session state lives under `LETMEKNOW_HOME`, by default the OS data directory: `~/.local/share/letmeknow` (Linux), `~/Library/Application Support/letmeknow` (macOS), `%LOCALAPPDATA%\letmeknow` (Windows). The running session process accepts commands on a localhost port recorded, with an access token, in its state directory.

## Develop

```bash
cd relay && npm install && npm test     # relay unit tests
python3 test/e2e.py                     # builds the client, runs it against a local relay
cd relay && npm run deploy              # deploy letmeknow.dev
```

CI runs the end-to-end test on Linux, macOS and Windows. Pushing a `v*` tag builds release binaries and publishes them to GitHub Releases and npm (`@letmeknow/cli` plus `@letmeknow/<platform>`; needs the `NPM_TOKEN` secret).

---
_Source: https://npm.io/package/@letmeknow/win32-x64 · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._