Skip to content

outlook changelog

io.github.rlrghb/outlook

4 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • server.json 1 field changed
    version
    1.16.1 1.16.3

  • AGENTS.md +4 −3

    https://raw.githubusercontent.com/rlrghb/olkcli/HEAD/AGENTS.md

    − - `make build`: build `bin/olk` with version ldflags.− - `make install`: build and copy to `$GOPATH/bin`.− - **macOS validation:** each `make build` produces a fresh (ad-hoc) binary identity, so the first run of the new `./bin/olk` that reads stored tokens triggers a macOS Keychain access prompt — a human must click **"Always Allow"**. An automated/agent run can't dismiss the dialog, so a hang on the first post-build command is expected (not a code bug); surface it for manual approval.+ - `make build`: build `bin/olk` with version ldflags and the `olk-dev` storage namespace (its own config directory and keychain entries; sign in once with `./bin/olk auth login`).+ - `make sign`: sign `bin/olk` with `OLK_CODESIGN_IDENTITY` so the Keychain grant survives rebuilds (macOS; see `docs/development.md`).+ - `make install`: build with the release namespace, `olk`, into `$(go env GOPATH)/bin`.+ - **macOS validation:** `./bin/olk` stores tokens under the `olk-dev` namespace, so it never reads or rewrites the Keychain items of an installed `olk`. Each `make build` still produces a fresh (ad-hoc) binary identity, so the first token-reading run after a rebuild can raise a macOS Keychain prompt for the `olk-dev` items — a human must click **"Always Allow"**. An automated/agent run can't dismiss the dialog, so a hang on the first post-build command is expected (not a code bug); surface it fo

  • server.json 1 field changed
    version
    1.15.1 1.16.1

  • AGENTS.md +2 −2

    https://raw.githubusercontent.com/rlrghb/olkcli/HEAD/AGENTS.md

    − - **Delegated mailbox routing**: read paths in `internal/graphapi/{mail,calendar,contacts}.go` take a `target string` first parameter and route through `c.targetUser(target)`. Empty target preserves `/me` behavior; a non-empty value hits `/users/{target}/…`. The CLI exposes this as the global `--mailbox` flag (env `OLK_MAILBOX`), validated once via `resolveMailboxTarget` in `internal/cmd/paging.go`. New read methods should follow the same shape. Writes are mixed: sending, replying, forwarding, m− - KQL search queries are always wrapped in double quotes (Graph `$search` parameter requirement). Property restrictions (`from:`, `subject:`, etc.) and boolean operators work inside the quotes. Literal double-quote characters are stripped from user input to prevent breaking the wrapper. See `internal/graphapi/mail.go`.+ - **Delegated mailbox routing**: read paths in `internal/graphapi/{mail,calendar,contacts}.go` take a `target string` first parameter and route through `c.targetUser(target)`. Empty target preserves `/me` behavior; a non-empty value hits `/users/{target}/…`. The CLI exposes this as the global `--mailbox` flag (env `OLK_MAILBOX`), validated once via `resolveMailboxTarget` in `internal/cmd/paging.go`. New read and write methods should follow the same shape. Every mailbox-scoped command takes a tar+ - KQL search queries are always wrapped in double quotes (Graph `$search` parameter requirement). Property restrictions (`from:`, `subject:`, etc.) and boolean operators work inside the quotes. Literal double-quote characters and backslashes in user input are escaped before wrapping to preserve the query. See `internal/graphapi/mail.go`.