docs: explain quickstart egress approvals (Fixes #5841)

[deepujain]

Summary

Adds the missing two-terminal network approval workflow to the OpenClaw quickstart where readers start terminal chat.
The quickstart now tells users to keep one terminal attached to the agent session and run openshell term in a second host terminal so blocked network egress requests can be approved or denied inline.

Fixes #5841

Changes

• docs/get-started/quickstart.mdx: Adds the two-terminal workflow, the openshell term command, and a link to the detailed approval guide.

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-only quickstart guidance; no runtime behavior changed.
• 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

• PR description includes the DCO sign-off declaration and every commit appears as Verified in GitHub
• Git hooks passed during commit and push, or npx prek run --from-ref main --to-ref HEAD passes
• Targeted tests pass for changed behavior
• Full npm test passes (broad runtime changes only) - attempted after npm run build:cli, but the local run timed out after 420s with environment-sensitive failures outside this docs 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) - passed with 0 errors and Fern's existing 2 warnings not printed by default.
• Doc pages follow the style guide (doc changes only)
• New doc pages include SPDX header and frontmatter (new pages only)

Evidence

• git diff --check passed.
• ./node_modules/.bin/prek run --from-ref upstream/main --to-ref HEAD passed.
• npm run docs passed outside the sandbox with 0 errors and 2 existing Fern warnings.
• npm run build:cli passed.
• npm test was attempted after the build, but did not complete within 420s locally; the observed failures were in environment-sensitive runtime suites such as Docker/gateway, real port probing, and platform-specific command behavior, not this docs-only quickstart change.

---

Signed-off-by: Deepak Jain deepujain@gmail.com

Summary by CodeRabbit

• Documentation
  • Updated the quickstart guide with clearer terminal-based setup instructions for chatting with the agent.
  • Added a two-terminal workflow for cases that may require network access, including how to monitor and approve or deny blocked requests.
  • Linked to additional guidance for handling agent network requests.

[copy-pr-bot]

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]

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: f9f0beb1-e0d6-4489-8e0b-d58d76adb551

📥 Commits

Reviewing files that changed from the base of the PR and between c1c7c1d and 1103a2a.

📒 Files selected for processing (1)

• docs/get-started/quickstart.mdx

---

📝 Walkthrough

Walkthrough

The quickstart’s terminal chat section now includes a two-terminal workflow for blocked network egress requests, with inline instructions to run openshell term and a link to the approval documentation.

Changes

Quickstart terminal workflow

Layer / File(s)	Summary
Terminal workflow update docs/get-started/quickstart.mdx	The “Chat with the Agent from the Terminal” section now describes using a second terminal to monitor and approve or deny blocked network egress requests, and adds a link to the approval guide.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A bunny hopped through quickstart land,
With two terminals close at hand.
One for the chat, one to approve,
For network hops that need a move.
Hop hop hooray—clear paths ahead! 🐰

🚥 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 is concise and accurately summarizes the docs update about quickstart egress approvals.
Linked Issues check	✅ Passed	The docs now explain the inline two-terminal workflow and mention openshell term as required by #5841.
Out of Scope Changes check	✅ Passed	The change is documentation-only and stays within the quickstart egress approval scope.
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.}

[wscurran]

✨ Thanks for adding the two-terminal network approval workflow to the OpenClaw quickstart with the openshell term command. This proposes a way to document the egress approval process so users can approve or deny blocked network requests inline.

---

Related open issues:

• #5841 [All Platforms][Docs] Quickstart guide omits two-terminal workflow and openshell term for network egress approval