docs(network-policy): add Gmail policy preset and integration example by Kunal-Somani · Pull Request #5415 · NVIDIA/NemoClaw

Kunal-Somani · 2026-06-14T13:29:41Z

Summary

Adds a least-privilege gmail network policy preset and a complete Gmail App Password workflow for Python scripts in NemoClaw sandboxes.
The preset and documentation now cover the IMAP attachment-download and SMTP send case reported in #3714 without claiming unsupported OAuth, service-account, or Gmail REST API behavior.

Related Issue

Closes #3714

Changes

nemoclaw-blueprint/policies/presets/gmail.yaml allows only /usr/bin/python3 to open raw TLS connections to imap.gmail.com:993 and smtp.gmail.com:465.
docs/network-policy/integration-policy-examples.mdx documents App Password prerequisites, safe upload/download commands, standard-library attachment and send examples, and credential/access cleanup.
test/gmail-policy.test.ts locks the exact hosts, ports, raw-TLS shape, and binary allowlist.
test/policies.test.ts includes gmail in preset discovery without increasing the file's ratcheted line budget.

Type of Change

Code change (feature, bug fix, or refactor)
Code change with doc updates
Doc only (prose changes, no code sample modifications)
Doc only (includes code sample changes)

Quality Gates

Tests added or updated for changed behavior
Existing tests cover changed behavior — justification:
Tests not applicable — justification:
Docs updated for user-facing behavior changes
Docs not applicable — justification:
Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging)
Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: Maintainer implementation narrows egress to exact Gmail hosts, ports, and /usr/bin/python3; test/gmail-policy.test.ts rejects broader endpoint or method policy.
Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:

Verification

PR description includes the DCO sign-off declaration and every commit appears as Verified in GitHub
Normal pre-commit, commit-msg, and pre-push hooks passed, or npm run check:diff passed when hooks were skipped or unavailable
Targeted behavior tests pass for the current change set, or tests are marked not applicable above — npx vitest run --project integration test/gmail-policy.test.ts test/policies.test.ts test/validate-config-schemas.test.ts (260 tests passed)
Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — not applicable to this focused preset and documentation change
Quality Gates section completed with required justifications or waivers
No secrets, API keys, or credentials committed
npm run docs builds without warnings (doc changes only) — 0 errors; two unrelated baseline warnings remain for unauthenticated redirect checking and existing light-theme contrast
Doc pages follow the style guide (doc changes only)
New doc pages include SPDX header and frontmatter (new pages only)

Additional validation: npm run checks, npm run typecheck:cli, npm run test:projects:check, npm run test-size:check, and syntax parsing for both embedded Python examples passed.

Signed-off-by: Kunal Somani kkunal_be23@thapar.edu

Summary by CodeRabbit

New Features
- Added a new Gmail preset for IMAP/SMTP access, including support for Gmail app-password-based workflows.
- Restricted the preset to approved Gmail mail endpoints and Python 3.
Documentation
- Expanded the integration policy guide with Gmail setup steps, preset usage, sandbox upload instructions, and sample email/attachment workflows.
- Added cleanup guidance for removing credentials and related files after use.

copy-pr-bot · 2026-06-14T13:29:44Z

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

coderabbitai · 2026-06-14T13:29:54Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 913a50ae-dd60-43be-9a73-73dafdf0f475

📥 Commits

Reviewing files that changed from the base of the PR and between 2864877 and 9d7702d.

📒 Files selected for processing (2)

docs/network-policy/integration-policy-examples.mdx
nemoclaw-blueprint/policies/presets/gmail.yaml

💤 Files with no reviewable changes (2)

nemoclaw-blueprint/policies/presets/gmail.yaml
docs/network-policy/integration-policy-examples.mdx

📝 Walkthrough

Walkthrough

This PR adds a new gmail network policy preset YAML that grants egress access to Gmail IMAP/SMTP endpoints and restricts interpreter binaries to python3, alongside documentation describing preset usage, sandbox credential upload, and Python examples for downloading attachments and sending email.

Changes

Gmail Network Policy Preset

Layer / File(s)	Summary
Gmail preset definition `nemoclaw-blueprint/policies/presets/gmail.yaml`	New `gmail` preset defines network enforcement (`gmail_mail`) allowing full egress to imap.gmail.com:993 and smtp.gmail.com:465 with `tls: skip`, and restricts allowed binaries to `/usr/bin/python3`.
Gmail integration documentation `docs/network-policy/integration-policy-examples.mdx`	Adds Gmail to the page description and Supported Integration Presets table, and introduces a "Gmail With an App Password" section covering prerequisites, policy-add/remove commands, sandbox credential upload with permission hardening, Python IMAP/SMTP examples, and cleanup steps.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: adding a Gmail policy preset and integration example.
Linked Issues check	✅ Passed	The PR matches `#3714` by adding a Gmail preset and tutorial-style docs for send/receive setup in NemoClaw.
Out of Scope Changes check	✅ Passed	The changes stay focused on Gmail policy support and documentation, with no obvious unrelated additions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

_{Comment @coderabbitai help to get the list of available commands.}

coderabbitai

Actionable comments posted: 1

🧹 Nitpick comments (1)

docs/network-policy/integration-policy-examples.mdx (1)
364-366: 💤 Low value

Consider active voice for prerequisites.

These lines use passive constructions ("enabled," "downloaded"). While acceptable in a requirements list, rephrasing in active voice improves clarity:

"Enable the Gmail API in a Google Cloud project."

"Create an OAuth2 client ID and client secret, or configure a service account with domain-wide delegation."

"Download a credentials.json file from the Google Cloud Console."
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/network-policy/integration-policy-examples.mdx` around lines 364 - 366,
The prerequisites list in the integration-policy-examples.mdx file uses passive
voice constructions that should be converted to active voice for improved
clarity. Rewrite the three prerequisite bullet points to start with action
verbs: replace "A Google Cloud project with the Gmail API enabled" with a
statement beginning with "Enable the Gmail API in a Google Cloud project",
replace the line about OAuth2 and service accounts with a statement beginning
with "Create an OAuth2 client ID and client secret, or configure a service
account", and replace "A credentials.json file downloaded from the Google Cloud
Console" with "Download a credentials.json file from the Google Cloud Console".
Keep all technical details and links intact while converting the grammatical
structure from passive to active voice.
Source: Coding guidelines

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@nemoclaw-blueprint/policies/presets/gmail.yaml`:
- Around line 8-39: There is a mismatch between the gmail preset and
documentation: the preset in nemoclaw-blueprint/policies/presets/gmail.yaml
(lines 8-39) defines REST API access but does not include the imap.gmail.com
endpoint on port 993, while the documentation in
docs/network-policy/integration-policy-examples.mdx (lines 435-449) provides an
IMAP connection example that requires this endpoint. Decide whether IMAP support
is in scope: if yes, add a new endpoint entry to the gmail_api policy in the
preset for imap.gmail.com on port 993 with appropriate protocol (connect or
tcp), and update the documentation statement around line 360 to clarify that
IMAP is supported; if no, remove the IMAP code example from the documentation
(lines 435-449) and keep only the REST API OAuth2 flow example.

---

Nitpick comments:
In `@docs/network-policy/integration-policy-examples.mdx`:
- Around line 364-366: The prerequisites list in the
integration-policy-examples.mdx file uses passive voice constructions that
should be converted to active voice for improved clarity. Rewrite the three
prerequisite bullet points to start with action verbs: replace "A Google Cloud
project with the Gmail API enabled" with a statement beginning with "Enable the
Gmail API in a Google Cloud project", replace the line about OAuth2 and service
accounts with a statement beginning with "Create an OAuth2 client ID and client
secret, or configure a service account", and replace "A credentials.json file
downloaded from the Google Cloud Console" with "Download a credentials.json file
from the Google Cloud Console". Keep all technical details and links intact
while converting the grammatical structure from passive to active voice.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: c1c3cbef-73c0-48d0-9b68-9c26dcc3ddd6

📥 Commits

Reviewing files that changed from the base of the PR and between 1f75d03 and 743ba65.

📒 Files selected for processing (2)

docs/network-policy/integration-policy-examples.mdx
nemoclaw-blueprint/policies/presets/gmail.yaml

wscurran · 2026-06-23T15:32:36Z

✨ Thanks for adding the Gmail network policy preset and integration example with OAuth2 and App Password workflows. This proposes a way to document Gmail API access setup for NemoClaw sandbox users.

Related open issues:

#3714 [NemoClaw]need tutorial on the best practice on enable gmail in NemoClaw

Signed-off-by: Kunal Somani <kkunal_be23@thapar.edu>

Kunal-Somani · 2026-06-24T08:33:14Z

✨ Thanks for adding the Gmail network policy preset and integration example with OAuth2 and App Password workflows. This proposes a way to document Gmail API access setup for NemoClaw sandbox users.

Related open issues:
* [#3714 [NemoClaw]need tutorial on the best practice on enable gmail in NemoClaw](https://github.com/NVIDIA/NemoClaw/issues/3714)

Thanks for taking a look and happy to make any adjustments if the preset or docs need tightening up.

Signed-off-by: Kunal Somani <kkunal_be23@thapar.edu>

cv

The proposed Gmail workflow does not solve the reported App-Password and attachment case: the preset excludes IMAP and SMTP while docs still upload an App Password; pip install lacks the pypi policy; localhost OAuth callback reachability is unexplained; service-account support is claimed but the sample does not implement it; and a Read and Send policy grants PUT, DELETE, and PATCH. Add a coherent supported auth path, credential cleanup, least-privilege endpoint and method policy, and semantic tests beyond preset-list presence.

Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>

cjagwani · 2026-07-08T20:57:52Z

@coderabbitai review

coderabbitai · 2026-07-08T20:57:57Z

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

apurvvkumaria · 2026-07-09T07:37:48Z

Exact head 9d7702daddd602c22bf375fcd30130114b5332d2 is mergeable with all current checks green, 9/9 targeted policy tests passing, no unresolved threads, and all seven commits GitHub Verified.

The current head addresses every item from the older change request: App Password-only IMAP/SMTP guidance, exact hosts/ports and /usr/bin/python3, standard-library examples without package-install egress, removal of OAuth/service-account claims, credential cleanup/revocation, and semantic policy coverage. CodeRabbit’s exact-head review produced no actionable findings.

@cv, please re-review or dismiss the outdated change request from b1d5368 when convenient. No merge action was taken.

## Summary Adds the pre-tag v0.0.79 release notes entry to `docs/about/release-notes.mdx` so the release plan can be generated after docs merge. The entry summarizes the merged v0.0.79 release train across inference, diagnostics, runtime hardening, policies, onboarding recovery, and release validation. ## Changes - Added the v0.0.79 release notes section with linked follow-up documentation for OpenRouter onboarding, managed vLLM changes, completion and logging, Deep Agents runtime limits, policy updates, onboarding recovery, and release validation. - Source summary: - #6461 -> `docs/about/release-notes.mdx`: Documents OpenRouter onboarding support and links to inference/provider references. - #6271 and #6272 -> `docs/about/release-notes.mdx`: Documents shell completion and structured logging highlights. - #6465, #6539, #6570, and #6528 -> `docs/about/release-notes.mdx`: Documents status route-drift, orphaned sandbox, gateway cleanup, and DGX Spark express-install diagnostics. - #6523, #6551, #6484, #6488, #6324, and #6542 -> `docs/about/release-notes.mdx`: Documents managed vLLM, Qwen3.6 tool parser, compaction, and timeout/readiness improvements. - #6559, #6538, #6560, #6568, #6552, #6567, and #6587 -> `docs/about/release-notes.mdx`: Documents runtime, credential, proxy, PID namespace, TOML, and provider-state hardening. - #6541, #5415, #6246, #6496, and #6573 -> `docs/about/release-notes.mdx`: Documents GitHub policy, Gmail policy, MCP allowlist, WhatsApp, and messaging-variant updates. - #6253, #6572, #6444, #6536, and #5860 -> `docs/about/release-notes.mdx`: Documents onboarding resume and create-step recovery improvements. - #6508, #6527, #5506, #6588, #6446, #6447, #6582, #6296, #6367, #6397, and #6505 -> `docs/about/release-notes.mdx`: Documents docs, release-risk, and E2E validation updates. ## Type of Change - [ ] Code change (feature, bug fix, or refactor) - [ ] Code change with doc updates - [x] Doc only (prose changes, no code sample modifications) - [ ] Doc only (includes code sample changes) ## Quality Gates  - [ ] Tests added or updated for changed behavior - [ ] Existing tests cover changed behavior — justification: - [x] Tests not applicable — justification: Release-note prose only. - [x] Docs updated for user-facing behavior changes - [ ] Docs not applicable — justification: - [ ] Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging) - [ ] Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: - [ ] Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue: ## Verification  - [x] PR description includes the DCO sign-off declaration and every commit appears as `Verified` in GitHub - [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed, or `npm run check:diff` passed when hooks were skipped or unavailable - [x] Targeted behavior tests pass for the current change set, or tests are marked not applicable above — command/result or justification: Tests not applicable, release-note prose only. - [ ] Applicable broad gate passed — `npm test` for broad runtime/test-harness changes; `npm run check` for repo-wide validation/coverage changes — command/result: - [x] Quality Gates section completed with required justifications or waivers - [x] No secrets, API keys, or credentials committed - [ ] `npm run docs` builds without warnings (doc changes only) - [x] Doc pages follow the [style guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md) (doc changes only) - [ ] New doc pages include SPDX header and frontmatter (new pages only) Docs validation note: `npm run docs:check-agent-variants && npm run docs:check-routes && git diff --check` passed. Full `npm run docs` is currently blocked before Fern validation because the pinned `fern-api@5.65.2` package is unavailable from npm (`ETARGET No matching version found`). ---  Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>  ## Summary by CodeRabbit * **Documentation** * Added release notes for v0.0.79 with a new summary of recent improvements, including onboarding and inference options, operator/CLI diagnostics, sandbox recovery hardening, runtime limits, network policy behavior, and release validation updates. * Added updated references and links for the latest release.

…NVIDIA#5415) ## Summary Adds a least-privilege `gmail` network policy preset and a complete Gmail App Password workflow for Python scripts in NemoClaw sandboxes. The preset and documentation now cover the IMAP attachment-download and SMTP send case reported in NVIDIA#3714 without claiming unsupported OAuth, service-account, or Gmail REST API behavior. ## Related Issue Closes NVIDIA#3714 ## Changes - `nemoclaw-blueprint/policies/presets/gmail.yaml` allows only `/usr/bin/python3` to open raw TLS connections to `imap.gmail.com:993` and `smtp.gmail.com:465`. - `docs/network-policy/integration-policy-examples.mdx` documents App Password prerequisites, safe upload/download commands, standard-library attachment and send examples, and credential/access cleanup. - `test/gmail-policy.test.ts` locks the exact hosts, ports, raw-TLS shape, and binary allowlist. - `test/policies.test.ts` includes `gmail` in preset discovery without increasing the file's ratcheted line budget. ## Type of Change - [ ] Code change (feature, bug fix, or refactor) - [x] Code change with doc updates - [ ] Doc only (prose changes, no code sample modifications) - [ ] Doc only (includes code sample changes) ## Quality Gates - [x] Tests added or updated for changed behavior - [ ] Existing tests cover changed behavior — justification: - [ ] Tests not applicable — justification: - [x] Docs updated for user-facing behavior changes - [ ] Docs not applicable — justification: - [x] Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging) - [x] Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: Maintainer implementation narrows egress to exact Gmail hosts, ports, and `/usr/bin/python3`; `test/gmail-policy.test.ts` rejects broader endpoint or method policy. - [ ] Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue: ## Verification - [x] PR description includes the DCO sign-off declaration and every commit appears as `Verified` in GitHub - [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed, or `npm run check:diff` passed when hooks were skipped or unavailable - [x] Targeted behavior tests pass for the current change set, or tests are marked not applicable above — `npx vitest run --project integration test/gmail-policy.test.ts test/policies.test.ts test/validate-config-schemas.test.ts` (260 tests passed) - [ ] Applicable broad gate passed — `npm test` for broad runtime/test-harness changes; `npm run check` for repo-wide validation/coverage changes — not applicable to this focused preset and documentation change - [x] Quality Gates section completed with required justifications or waivers - [x] No secrets, API keys, or credentials committed - [ ] `npm run docs` builds without warnings (doc changes only) — 0 errors; two unrelated baseline warnings remain for unauthenticated redirect checking and existing light-theme contrast - [x] Doc pages follow the [style guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md) (doc changes only) - [ ] New doc pages include SPDX header and frontmatter (new pages only) Additional validation: `npm run checks`, `npm run typecheck:cli`, `npm run test:projects:check`, `npm run test-size:check`, and syntax parsing for both embedded Python examples passed. --- Signed-off-by: Kunal Somani <kkunal_be23@thapar.edu> --------- Signed-off-by: Kunal Somani <kkunal_be23@thapar.edu> Signed-off-by: Apurv Kumaria <akumaria@nvidia.com> Co-authored-by: Apurv Kumaria <akumaria@nvidia.com>

## Summary Adds the pre-tag v0.0.79 release notes entry to `docs/about/release-notes.mdx` so the release plan can be generated after docs merge. The entry summarizes the merged v0.0.79 release train across inference, diagnostics, runtime hardening, policies, onboarding recovery, and release validation. ## Changes - Added the v0.0.79 release notes section with linked follow-up documentation for OpenRouter onboarding, managed vLLM changes, completion and logging, Deep Agents runtime limits, policy updates, onboarding recovery, and release validation. - Source summary: - NVIDIA#6461 -> `docs/about/release-notes.mdx`: Documents OpenRouter onboarding support and links to inference/provider references. - NVIDIA#6271 and NVIDIA#6272 -> `docs/about/release-notes.mdx`: Documents shell completion and structured logging highlights. - NVIDIA#6465, NVIDIA#6539, NVIDIA#6570, and NVIDIA#6528 -> `docs/about/release-notes.mdx`: Documents status route-drift, orphaned sandbox, gateway cleanup, and DGX Spark express-install diagnostics. - NVIDIA#6523, NVIDIA#6551, NVIDIA#6484, NVIDIA#6488, NVIDIA#6324, and NVIDIA#6542 -> `docs/about/release-notes.mdx`: Documents managed vLLM, Qwen3.6 tool parser, compaction, and timeout/readiness improvements. - NVIDIA#6559, NVIDIA#6538, NVIDIA#6560, NVIDIA#6568, NVIDIA#6552, NVIDIA#6567, and NVIDIA#6587 -> `docs/about/release-notes.mdx`: Documents runtime, credential, proxy, PID namespace, TOML, and provider-state hardening. - NVIDIA#6541, NVIDIA#5415, NVIDIA#6246, NVIDIA#6496, and NVIDIA#6573 -> `docs/about/release-notes.mdx`: Documents GitHub policy, Gmail policy, MCP allowlist, WhatsApp, and messaging-variant updates. - NVIDIA#6253, NVIDIA#6572, NVIDIA#6444, NVIDIA#6536, and NVIDIA#5860 -> `docs/about/release-notes.mdx`: Documents onboarding resume and create-step recovery improvements. - NVIDIA#6508, NVIDIA#6527, NVIDIA#5506, NVIDIA#6588, NVIDIA#6446, NVIDIA#6447, NVIDIA#6582, NVIDIA#6296, NVIDIA#6367, NVIDIA#6397, and NVIDIA#6505 -> `docs/about/release-notes.mdx`: Documents docs, release-risk, and E2E validation updates. ## Type of Change - [ ] Code change (feature, bug fix, or refactor) - [ ] Code change with doc updates - [x] Doc only (prose changes, no code sample modifications) - [ ] Doc only (includes code sample changes) ## Quality Gates  - [ ] Tests added or updated for changed behavior - [ ] Existing tests cover changed behavior — justification: - [x] Tests not applicable — justification: Release-note prose only. - [x] Docs updated for user-facing behavior changes - [ ] Docs not applicable — justification: - [ ] Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging) - [ ] Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: - [ ] Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue: ## Verification  - [x] PR description includes the DCO sign-off declaration and every commit appears as `Verified` in GitHub - [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed, or `npm run check:diff` passed when hooks were skipped or unavailable - [x] Targeted behavior tests pass for the current change set, or tests are marked not applicable above — command/result or justification: Tests not applicable, release-note prose only. - [ ] Applicable broad gate passed — `npm test` for broad runtime/test-harness changes; `npm run check` for repo-wide validation/coverage changes — command/result: - [x] Quality Gates section completed with required justifications or waivers - [x] No secrets, API keys, or credentials committed - [ ] `npm run docs` builds without warnings (doc changes only) - [x] Doc pages follow the [style guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md) (doc changes only) - [ ] New doc pages include SPDX header and frontmatter (new pages only) Docs validation note: `npm run docs:check-agent-variants && npm run docs:check-routes && git diff --check` passed. Full `npm run docs` is currently blocked before Fern validation because the pinned `fern-api@5.65.2` package is unavailable from npm (`ETARGET No matching version found`). ---  Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>  ## Summary by CodeRabbit * **Documentation** * Added release notes for v0.0.79 with a new summary of recent improvements, including onboarding and inference options, operator/CLI diagnostics, sandbox recovery hardening, runtime limits, network policy behavior, and release validation updates. * Added updated references and links for the latest release.

Add the shrike-security preset to the supported-presets table and a short integration section following the Gmail-preset precedent (NVIDIA#5415): apply commands, credential activation note, and the enforce contract. Signed-off-by: Habirua <samarow29@gmail.com>

coderabbitai Bot reviewed Jun 14, 2026

View reviewed changes

Comment thread nemoclaw-blueprint/policies/presets/gmail.yaml Outdated

wscurran added area: docs Documentation, examples, guides, or docs build area: policy Network policy, egress rules, presets, or sandbox policy labels Jun 23, 2026

Kunal-Somani added 2 commits June 24, 2026 13:03

docs(network-policy): add Gmail policy preset and integration example

1894c41

Signed-off-by: Kunal Somani <kkunal_be23@thapar.edu>

docs(network-policy): remove IMAP example from Gmail preset docs

0c472ab

Signed-off-by: Kunal Somani <kkunal_be23@thapar.edu>

Kunal-Somani force-pushed the docs/gmail-policy-preset-and-integration-example branch from bece3ce to cb8ee6d Compare June 24, 2026 08:26

test(policies): add gmail to expected preset list

b1d5368

Signed-off-by: Kunal Somani <kkunal_be23@thapar.edu>

Kunal-Somani force-pushed the docs/gmail-policy-preset-and-integration-example branch from 2864877 to b1d5368 Compare June 24, 2026 12:46

cv added the v0.0.76 Release target label Jul 7, 2026

cv requested changes Jul 7, 2026

View reviewed changes

wscurran added v0.0.77 Release target and removed v0.0.76 Release target labels Jul 7, 2026

apurvvkumaria self-assigned this Jul 7, 2026

apurvvkumaria added 2 commits July 7, 2026 14:22

merge: sync Gmail policy PR with main

7bd2c02

Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>

fix(network-policy): support Gmail App Password workflow

90d40ff

Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>

ericksoa added v0.0.78 Release target and removed v0.0.77 Release target labels Jul 8, 2026

cjagwani added v0.0.79 Release target and removed v0.0.78 Release target labels Jul 8, 2026

apurvvkumaria added 2 commits July 8, 2026 11:39

merge: sync Gmail policy PR with main

8e9b2e4

Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>

test(policy): include Gmail in preset catalog

9d7702d

Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>

apurvvkumaria enabled auto-merge (squash) July 8, 2026 19:15

cjagwani requested a review from cv July 9, 2026 05:05

cv approved these changes Jul 9, 2026

View reviewed changes

apurvvkumaria merged commit cd32875 into NVIDIA:main Jul 9, 2026
34 checks passed

cv mentioned this pull request Jul 9, 2026

docs: add Gmail policy guidance #6438

Closed

21 tasks

jyaunches mentioned this pull request Jul 9, 2026

docs: prepare v0.0.79 release notes #6594

Merged

21 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

docs(network-policy): add Gmail policy preset and integration example#5415

docs(network-policy): add Gmail policy preset and integration example#5415
apurvvkumaria merged 7 commits into
NVIDIA:mainfrom
Kunal-Somani:docs/gmail-policy-preset-and-integration-example

Kunal-Somani commented Jun 14, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

copy-pr-bot Bot commented Jun 14, 2026

Uh oh!

coderabbitai Bot commented Jun 14, 2026 •

edited

Loading

Reviews paused

Walkthrough

Changes

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

wscurran commented Jun 23, 2026

Uh oh!

Kunal-Somani commented Jun 24, 2026

Uh oh!

cv left a comment

Uh oh!

cjagwani commented Jul 8, 2026

Uh oh!

coderabbitai Bot commented Jul 8, 2026 •

edited

Loading

Uh oh!

apurvvkumaria commented Jul 9, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Uh oh!

Conversation

Kunal-Somani commented Jun 14, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Related Issue

Changes

Type of Change

Quality Gates

Verification

Summary by CodeRabbit

Uh oh!

copy-pr-bot Bot commented Jun 14, 2026

Uh oh!

coderabbitai Bot commented Jun 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviews paused

Walkthrough

Changes

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

wscurran commented Jun 23, 2026

Uh oh!

Kunal-Somani commented Jun 24, 2026

Uh oh!

cv left a comment

Choose a reason for hiding this comment

Uh oh!

cjagwani commented Jul 8, 2026

Uh oh!

coderabbitai Bot commented Jul 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

apurvvkumaria commented Jul 9, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Kunal-Somani commented Jun 14, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Jun 14, 2026 •

edited

Loading

coderabbitai Bot commented Jul 8, 2026 •

edited

Loading