Repository navigation
Conversation
|
Cosmo, Jai's AI assistant. Upstream preparationChecked AGENTS.md, VISION.md, CI and the organization defaults. Neither repository has a PR template or CONTRIBUTING.md. This description uses the Summary and Verification structure of merged PR #1024, mention/reaction metadata. The written merge bar is focused changes, review, regression tests, user-facing docs/changelog updates and live Google proof where behavior depends on Workspace APIs. Wider commands and API contracts need discussion first.
Additional dogfood evidence to collect, beyond the explicit written requirements:
IntentExpose rich Google Chat data through native commands and opt-in full JSON, plus text update and deletion. Keep compact defaults, scopes, read-only behavior and explicit reply deletion. Dogfood before submitting upstream. Reviewers
Act on
ConsiderNone of the remaining suggestions blocks this patch. Noted
Dismissed
Agreement mapBoth models independently identified the identifier trust gap. Grok alone found missing forwarded/quoted classifications; the actual SDK fixtures reproduced them. Claude alone found the loose live assertion and upstream preparation friction; both were confirmed. The remaining suggestions concern optional structure or extra coverage. The corrected build is active on Borg Cube 04, Borg Cube 03, the Mac Mini Jai/Jai Work profiles, VOC and Grokbot through their existing command paths. Previous binaries are backed up. Gateways and stored account configuration were not changed. Borg Cube 03 was completed on October 16; Grokbot and the validated upstream update were completed on October 17. Post-activation compatibility: the Mini Jai Work account and all six saved accounts across VOC Sysops, Incident Triage and shared FINN passed read-only Chat space reads. An initial Sysops account read returned authentication exit 4 once; the complete follow-up passed with no credential/configuration change. Its cause is unconfirmed. Binary hashes and rollback provenance are recorded privately on each host. 2026-10-17 maintenance evidence
The personal draft remains open. No upstream PR has been submitted; focused proposals still await the upstream scope discussion and Jai's decision after dogfooding. 2026-10-18 maintenance evidence
The personal PR stays draft. Technical Chat validation remains strong; focused upstream proposals still await the scope discussion and Jai's instruction. 2026-10-19 maintenance evidence
The personal PR stays draft. Technical evidence supports preparing focused upstream proposals; scope discussion and Jai's instruction still precede submission. 2026-10-20 maintenance evidence
The personal PR remains draft. Technical proof supports preparing focused upstream proposals; the scope discussion and Jai's instruction still precede submission. 2026-10-21 maintenance evidence
The personal PR stays draft. Technical Chat evidence supports focused proposals; upstream scope discussion and Jai's instruction still precede submission. Rekey integration repairs should be proposed separately if authorized. 2026-10-22 maintenance evidence
The personal PR stays draft. Technical Chat evidence supports preparing focused proposals; upstream scope discussion and Jai's instruction still precede submission. 2026-10-23 maintenance evidence
The personal PR stays draft. Technical Chat evidence supports focused upstream proposals; scope discussion and Jai's instruction still precede submission. 2026-10-24 maintenance evidence
The personal PR stays draft. Technical evidence supports focused Chat proposals; Jai's scope decision still precedes upstream submission. 2026-10-26 fleet audit
The personal PR remains draft. Existing Chat proof still supports focused upstream proposals, subject to Jai's scope decision. No upstream PR has been opened. 2026-10-27 maintenance evidence
The personal PR stays draft. Technical evidence supports preparing focused Chat proposals; upstream scope discussion and Jai's instruction remain required before submission. Relay configuration, credentials, account routing and gateways were preserved. 2026-10-28 maintenance evidence
The personal PR stays draft. Technical evidence supports preparing focused Chat proposals; upstream scope discussion and Jai's instruction still precede submission. Existing grants, live keyrings, credentials, account routing and relay configuration were preserved. This was binary maintenance and synthetic local protocol testing, with no Executor migration. 2026-10-31 fleet audit
2026-11-02 audit method correction
2026-11-04 security automation integration
Technical Chat evidence continues to support focused upstream proposals. This personal PR remains draft; no upstream submission is authorized. Launchers, gateways, Homebrew, native CA stores, Google grants and relay routing were preserved. 2026-11-05 release tag enforcement integration
The personal PR stays draft. Technical Chat evidence supports focused proposals after scope discussion; no upstream PR is authorized or opened. 2026-11-06 upstream v0.48.0 integration
2026-11-09 upstream attachment proposalThe open upstream proposal adds attachment summaries to compact JSON message lists and a separate download command that writes local files. Its metadata overlaps fields already available through the fork’s typed full reads. If it lands, check the resulting compact schema during the next integration. The existing dogfood evidence still supports focused proposals for typed full reads, formatted hyperlinks, CardsV2 and narrow text mutations. Open upstream attachment PR 2026-11-12 placeholder account documentation
2026-11-15 Workspace contract fixes and dependency refresh
2026-11-16 Mac Mini and VOC rollout
2026-11-17 v0.48.1 release syncVerified fork head Independent review, local CI, hooks, 15 pinned worker tests, 66 isolated CLI invocations, 20 loopback executions, 12 live Chat checks and all ten exact-head checks passed. All four owned Chat fixtures were removed. The complete listing was empty. CI Both Borg hosts, Mini Jai and Jai Work, and VOC match the validated source and artifact hashes. Accessible accounts passed paired reads, including 11 VOC entries. 6 VOC profiles have preview proof only. One retained the same keyring permission failure on both builds. Mini Jai Work's historical login still selects stock Gog. Trusted Grokbot remains offline. 2026-11-19 contributor guidance syncValidated signed source 2026-11-21 dependency refreshValidated signed source 2026-11-22 problem-first PR guidanceCosmo, Jai's AI assistant. Validated signed head Independent Codex review, hooks, local CI, pinned worker checks/all 15 tests, 66 isolated CLI invocations, 20 loopback executions, all 12 live Chat checks and all ten hosted checks passed. CodeQL analyzed the matching tree. Caller-only privacy was proved before writes; four owned messages were cleaned and final listing was empty. CI Four reachable hosts match intended source, hashes and provenance. Accessible paired reads passed, including 11 VOC entries; 6 VOC contexts remain preview-only. Known raw/login PATH and matching keyring failures persist. Trusted Grokbot remains offline. |
* chore: open next unreleased section * chore: restore development metadata after v0.45.0 --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Peter Steinberger <steipete@gmail.com>
…aw#1221) Rewrite `gog auth <email>` to `gog auth add <email>` when the first token after the top-level auth command contains an @ and is not an auth subcommand. Bare `gog auth` and mistyped subcommands keep their existing Kong errors.
Update Vitest to 5.0.5 and Cloudflare Workers types to 5.20261015.1 with matching lockfile entries. Preserve the worker's 24-hour release cooldown, pinned pnpm 11.28.5, security overrides, and Go requirements. Validated with the frozen lockfile, full worker gate, independent Codex review, and exact-head CI. No production configuration or deployment changes.
…nclaw#1215) Preserve paragraph breaks in forward notes and add opt-in HTML-note inputs to both send and draft forwarding. Share existing reply conversion rules without changing ordinary forward defaults or reply behavior. Document image-only alternatives and preserve signature placement. Closes openclaw#1215. Maintainer product direction approved. Validation: base-failing/head-passing send and draft regression; focused composition tests; full make ci; govulncheck with no reachable vulnerabilities; independent review with no actionable P0-P2 findings; exact-head cross-platform CI. Co-authored-by: Malo Bourgon <mbourgon@gmail.com>
Migrate repository-local macOS CI and release preflight from macos-15 to xcode-27 while preserving macOS 15.0 and Go 1.26.0 support. Make the Darwin deployment target explicit in cgo compiler/linker flags, preventing reuse of cached macOS 27 objects, and verify the built binary's minimum OS. Keep the shared release workflow at v1 for the centrally managed migration. Update actionlint, the release guide, and changelog. Validation: actionlint, independent Codex review through P2, warning-free native build and minos 15.0 verification. Remote make ci, govulncheck, and exact-head GitHub CI are recorded in the task report.
Replace the App-key dispatcher with OIDC-only Worker intake. No App key and no token mints remain in this workflow. The App webhook remains the independent route; the Worker owns eligibility and best-effort acknowledgements. Canonical migration: openclaw/clawsweeper#2062 Validated with actionlint, zizmor --offline (zero template-injection findings), no secrets. references, and independent autoreview.
The Google Drive SDK dropped requested false booleans during JSON encoding. Preserve requested top-level flags, including default starred and hasThumbnail, while retaining omission for conditionally absent fields and nested booleans. Document the exact-response alternative. The regression fails on the previous main and passes with the fix. Focused tests, make ci, and independent Codex review passed; govulncheck found no reachable vulnerabilities. Co-authored-by: postoso <postoso@users.noreply.github.com>
Refresh the Google API client and golangci-lint, along with eligible worker types, Wrangler, PostCSS and Undici updates. Regenerate the lockfile using pnpm 11.28.5 and retain the Go 1.26 minimum, Node 26, pnpm 11, and 24-hour worker cooldown. Validation: Linux make ci, worker frozen install/lint/typecheck and 15 tests, and independent Codex review passed. govulncheck found no reachable vulnerabilities; only the unimported OpenPGP advisory remains with no fixed version.
Add GOG_GOOGLE_API_BASE_URL for mocks, emulators, and relays that attach credentials outside gog. Use a plain transport without resolving local credential providers, preserve the request path/query and original host, and refuse cross-origin redirects while retaining command and read-only policies. Full Linux make ci and independent review passed. The built CLI reached a synthetic relay without Authorization and refused a cross-origin redirect with zero requests to the target. Exact-head Linux, Windows, macOS, minimum-Go, worker, and Docker CI are green. Closes openclaw#1225 Co-authored-by: km-tr <kumagai@bear.tokyo>
Peter explicitly accepted PR openclaw#1224 on 2026-10-20. The secrets code was reviewed in-session without uploading it to the review service; Peter's external-review exception applies only to this PR. Isolated Codex review of CLI/documentation found no actionable P0–P2 issue. Fixed source-lock bypass and destructive output replacement found during review. Hold the shared store lock through reading, staging, verification and publication; independently verify every item and its metadata; fsync before atomic Linux/macOS directory exchange; roll back publication failures and retain recovery paths if rollback also fails. Clear decrypted byte buffers where practical. Preserve legacy and encoded formats and keep live credential files unchanged. Windows uses a fresh output path, flushed ciphertext and a write-through rename; existing output is refused safely where atomic directory exchange is unavailable. Validation: full `make ci` passed on an isolated Linux runner; focused rekey/CLI tests and secrets race tests passed. `govulncheck ./...` found no reachable vulnerability; GO-2026-5932 affects the unimported OpenPGP package only. All exact-head GitHub CI checks passed: [run 39474735303](https://github.com/openclaw/gogcli/actions/runs/39474735303). No release is part of this landing. Co-authored-by: Søren L. Hansen <sorenisanerd@gmail.com>
Align forwarded headers in both MIME parts with Gmail's formatting: linked sender/recipient addresses, plain labels, and two blank lines before the original body. Reuse the mailbox rendering helpers without changing reply attribution behavior. Validated the baseline mismatch on synthetic headers; focused forward tests and the full make ci gate pass. Independent Codex review found no actionable P0–P2 findings. The contributor supplied live Gmail draft/readback evidence. Closes openclaw#1236. Co-authored-by: Malo Bourgon <mbourgon@gmail.com>
Build release and Docker binaries with Go 1.27.3 and run minimum-series CI with Go 1.26.10, addressing GO-2026-6809 while retaining the Go 1.26.0 minimum. Pin the matching official Docker image digest and refresh the Google API client and generated definitions. Validation: Docker consistency regressions, independent Codex P0–P2 review, full remote make ci, zero reachable govulncheck findings, and exact-head cross-platform CI. Worker updates inside the 24-hour release cooldown remain deferred.
Prepare the 0.46.0 minor release for new auth commands, Google API relay support, Gmail forwarding improvements, and the Go security update. Preserve all 11 Unreleased entries verbatim, reorder them by user impact, add a one-line highlight, and set the embedded version to v0.46.0. Validation: unchanged bullet multiset, independent Codex P0–P2 review, full remote make ci, and exact-head cross-platform CI. The prior merged-toolchain release dry run passed. Publication requires a separate successful 0.46.0 dry run on this release-prep merge.
Update Wrangler, Workers types, Oxlint, and Oxfmt within the tracking worker's 24-hour release cooldown. Preserve runtime floors and supply-chain policy; include the update in the unpublished 0.46.0 notes. Validation: make worker-ci on Node 26.12.0 and pnpm 11.28.5, independent review, and exact-head GitHub Actions.
Restore the versioned Unreleased heading and development source version after the verified 0.46.0 publication. Preserve all published release notes. Validation: focused documentation/version checks, independent review, and exact-head CI.
Read push and webhook tokens from named environment variables while preserving literal flags, stored-hook defaults, validation, and secret-free previews. Refs openclaw#1292. Co-authored-by: Michael Appel <mappel@nvidia.com>
Keep the friendly missing-document message while retaining the API error cause so affected Docs commands use the documented not_found exit code 5. Fixes openclaw#1288. Verified through built CLI before/after comparisons, regression tests, independent review, and exact-head CI. Co-authored-by: HardMax71 <maxymazatyan@gmail.com>
build(deps): refresh Go clients and worker tooling Retain the Go 1.26 minimum, patched build toolchain, pnpm version, release cooldown, and security overrides while advancing tested patch/minor updates.
New backups no longer select a maintainer-owned repository. They commit locally until the user configures a remote, and the CLI explains local-only operation. Explicit saved remotes and existing Git origins continue to work without rewrites; checkpoint uploads follow the same rule. Closes openclaw#1287. Validation: the default-remote regression fails on the previous implementation. Synthetic tests pass for local initialization, snapshot/checkpoint commits without a remote, and pushing to a temporary bare Git origin. No real backup or Google-account access was performed. The backup guide documents explicit remote setup. Independent Codex P0–P2 review is clean. Full gate: `make ci` and `govulncheck ./...` passed on the dedicated Linux Crabbox lease (run `run_8ec2e0593acf4e96b1e01faab914ef5a`). Govulncheck found no reachable vulnerabilities.
…arches Reject equal or reversed Calendar windows with a usage error before requesting events, and make a far-future search with only --from usable by ending it 90 days after that start. Successful historical --from-only searches retain their existing end at now + 90 days. Explicit time ranges and historical timezone offsets keep their intended instants. Closes openclaw#1280. Validation: synthetic Calendar HTTP regressions fail on the old implementation for far-future searches, invalid ranges, and historical offset seconds. The focused Calendar suite passes, including a compatibility regression for historical open-ended searches. No live Google Calendar data was used. Full gate: `make ci` passed on the dedicated Linux Crabbox lease (run `run_5b7894aafd5fe2d0f467bb6b930a7f50`). Independent Codex P0–P2 final review is clean. Co-authored-by: Steven Huang <134844631+remote-controlled-man@users.noreply.github.com>
Add optional --keyring storage to auth service-account set. Existing JSON key files remain the default and continue to work. Keyring-backed files contain only a reference, resolved consistently by status, authentication, and Keep. Each saved reference gets its own keyring entry so separate configurations cannot overwrite each other's credentials. A failed reference write preserves the old credential and removes the new entry. The auth guide documents migration into keyring storage, returning to files, recovery copies, and older-version compatibility. Generic legacy managed key files are removed after a successful migration; caller-owned input files and separate Keep-specific files remain untouched. Validation uses synthetic keys and injected stores: file/keyring round trips, legacy migration, independent layouts, failed reference writes, cleanup, CLI status, and Keep resolution. No live account consent or real key migration was performed. Full gate: `make ci` passed on the dedicated Linux Crabbox lease (run `run_eda6c371372b6e4a77c433a9bfe59c78`). Independent Codex P0–P2 final review is clean. Co-authored-by: Tommy Joseph <64457309+tommyjoseph@users.noreply.github.com>
Automatic reauthorization now carries the command runtime and OAuth client dependencies into the callback. Expired-token recovery can reach the normal authorization path and retry the original request while retaining cancellation, the selected client, and the stored grant. Closes openclaw#1277. Synthetic proof reproduces the former missing-runtime error and verifies the runtime, credentials reader, token store, client resolver, cancellation, and original service/scope set. Existing retry-transport tests cover retrying with the refreshed token. No live consent run happened. Full gate: `make ci` passed on the dedicated Linux Crabbox lease (run `run_dd52ab96aef020f29094b43ae82ea568`). Independent Codex P0–P2 final review is clean. Co-authored-by: Vitor Cepeda Lopes <vitor@vitorcepedalopes.com>
Give every regular attachment and inline part a unique X-Attachment-Id. IDs combine the original attachment index and a content digest, remaining stable when the same attachments are rebuilt while distinguishing duplicate files. Regular attachment Content-IDs match their attachment IDs; quoted inline images retain their original Content-IDs. Closes openclaw#1299. Generated-MIME proof parses nested multipart parts, verifies uniqueness and matching Content-IDs, preserves the original inline CID, and checks stable IDs across independent builds with duplicate attachment bytes. The regressions fail on the old implementation. Draft composition parity and inline attachment tests pass. Delivered-Gmail behavior is contributor-reported; no live Gmail send, delivery, or draft-edit test was performed. Full gate: `make ci` passed on the dedicated Linux Crabbox lease (run `run_8ffa60b899555b831ea3472d711aa5c7`). Independent Codex P0–P2 final review is clean. Co-authored-by: Mattia Trapani <mattia.trapani@gmail.com>
Allow a local backup repository to acquire its first configured origin. After `gog backup init` without a remote, `gog backup init --remote URL` now adds the missing origin so subsequent pushes use it. Existing origins are never replaced, even when a different remote is supplied in configuration. Follow-up to openclaw#1303 and openclaw#1287. Synthetic proof first reproduced the missing-origin failure, then verified initialization, a push to a temporary local bare repository, and preservation of the existing origin. No real backup was run or personal configuration changed. Full gate: `make ci` passed on the dedicated Linux Crabbox lease (run `run_1fd82869a516d40c0c3e78f16c0b3efc`). Independent Codex P0–P2 final review is clean.
Finalize the 0.48.0 minor release notes and version for local-by-default backups, optional service-account keyring storage, ID-only Gmail search, and environment-backed watch tokens. Preserve all 21 existing release-note bullets and contributor credit, and explicitly disclose the delivered-Gmail and OAuth consent validation limits. Validation: exact-head CI green; independent P0–P2 review clean; full make ci and govulncheck passed on the dedicated Linux lease. No reachable vulnerabilities and no real backup performed.
Give the complete command-package test suite a finite twenty-minute timeout in make test and minimum-Go CI. Preserve every test and existing toolchain. The main minimum-Go failure exhausted Go's default ten-minute package budget during normal schema work. The named test passes in 1.53s on Go 1.26.10; independent P0–P2 review and all exact-head CI checks pass.
Restore the next development cycle after v0.48.0: one 0.48.1 Unreleased section and v0.48.0-dev version metadata, preserving the published release notes. Release-closeout tests, independent P0–P2 review, and all exact-head CI checks pass. The published release and its channels have been independently verified.
Replace the four Clawdbot account examples with generic placeholders and clarify which authenticated account to supply. Record the documentation update in the changelog. Validation: Codex review, five documentation-checker tests, all five repository CI jobs, and CodeQL passed.
Consolidate reproduced command bugs from openclaw#1308, openclaw#1311-openclaw#1319, openclaw#1321-openclaw#1326 and issues openclaw#1328, openclaw#1329, openclaw#1330, openclaw#1331, openclaw#1335. Co-authored-by: Bobby Bones <159389674+saariuslystoned@users.noreply.github.com> Co-authored-by: Sebastien Tardif <sebtardif@ncf.ca>
Patch the Go build toolchain for reachable GO-2026-6859 while preserving the Go 1.26.0 source minimum. Refresh Google clients, networking dependencies, and tracking-worker tooling without weakening the release cooldown or security overrides. Validated with the full Go and worker gates, govulncheck, independent P0–P2 review, and exact-head CI.
Finalize the v0.48.1 patch release changelog and embedded version. Preserve all existing release notes and contributor credits; include highlights for safer Gmail replies, Calendar fixes, and Go security updates. Validation: make ci and govulncheck ./... passed on AWS Crabbox; independent Codex autoreview scoped-clean through P2; all PR checks passed at 0ec5513.
Restore the versioned 0.48.2 Unreleased section and v0.48.1-dev embedded version after the verified v0.48.1 release. Preserve all published notes and contributor credits. Validation: changelog preservation and heading uniqueness checks passed; independent Codex autoreview is scoped-clean through P2; exact-head CI 43818414106, CodeQL, and Docker passed at 7cd0bcd.
Co-authored-by: hannesrudolph <49103247+hannesrudolph@users.noreply.github.com>
) Refresh MCP, Google API and protocol modules, Go networking, OpenTelemetry auto SDK, and tracking-worker dependencies while retaining runtime floors, the 24-hour worker cooldown, and security overrides. Verified with make ci, worker checks, govulncheck, dependency audit, independent P0–P2 review, and exact-head cross-platform CI.
What Problem This Solves
Scripts reading compact Chat messages cannot inspect named hyperlink targets, cards or image metadata. People correcting or removing their own Chat messages also need native editing and deletion commands for their daily workflow.
User Impact
Opt-in
--fullon list and search and native message get expose SDK-modeled formatted text, CardsV2, image references and attachment metadata. Compact JSON and plain-text defaults stay compatible. Text updates useupdateMask=text, and deleting threaded replies requires--delete-replies.Full output follows the typed SDK contract. Images remain references and metadata. Read-only guards and untrusted-content wrapping apply.
Why This Change Was Made
The personal fork reuses the existing SDK and OAuth scopes for rich reads and text mutations. Append-only upstream merges keep it current while dogfooding. The latest merge changes only reviewer instructions in the PR template; application behavior, dependencies and inherited workflows are unchanged.
The PR stays open as a draft. Focused upstream proposals need Jai's scope decision.
Evidence
Validated source
b22e04289aceaf030a4fd69fd6ef633e8cf45a02includes upstream31c4e14186e8cbbc0d9ba4514dda3c64880d1c9aand v0.48.1.Weekly default-branch CodeQL scheduling awaits a separately authorized fork main update.