Skip to content

docs(execute_code): document project/strict execution modes#12073

Merged
teknium1 merged 1 commit into
mainfrom
hermes/execute-code-mode-docs
Apr 18, 2026
Merged

docs(execute_code): document project/strict execution modes#12073
teknium1 merged 1 commit into
mainfrom
hermes/execute-code-mode-docs

Conversation

@teknium1

@teknium1 teknium1 commented Apr 18, 2026

Copy link
Copy Markdown
Contributor

Summary

Follow-up to PR #11971 — documents the new code_execution.mode config key on the docs site so users can actually find and configure it.

What changed

File Change
user-guide/configuration.md Code Execution block: add mode: project to the yaml example with two-line explanation of project vs strict and a note that security invariants are identical across modes
user-guide/features/code-execution.md New Execution Mode section with comparison table and usage guidance; update the 'temporary directory' paragraph so it reflects that script.py runs in session CWD in project mode (staging dir stays on PYTHONPATH for imports); drop stale 'sandboxed' framing from the intro and skill-passthrough paragraph
getting-started/learning-path.md One-line Code Execution summary updated (the default no longer 'runs code in sandboxed environments' — it runs in the session's real working directory)

Rationale for dropping 'sandboxed' language

Commit 39b83f34 removed 'sandbox' wording from the tool schema because agents on local backends falsely believed they were sandboxed and refused networking tasks. Same concern for user docs — 'sandboxed Python execution' sets an incorrect mental model now that project mode is the default and scripts run in the user's actual working directory with their real venv python. The docs now call it what it is: a Python child process with RPC back to Hermes, running under a configurable mode.

Validation

  • No code changes.
  • Local npm run build (Docusaurus) succeeds; only pre-existing warnings (broken anchor in nix-setup.md, broken link in docker.md) — unrelated to this PR.

@teknium1
docs(execute_code): document project/strict execution modes
cfc7f54 
Follow-up to PR #11971. Documents the new code_execution.mode config
key and what each mode actually does.

- user-guide/configuration.md: add mode: project to the yaml example,
  explain project vs strict and call out that security invariants are
  identical across modes.
- user-guide/features/code-execution.md: new 'Execution Mode' section
  with a comparison table and usage guidance; update the 'temporary
  directory' note so it reflects that script.py runs in the session
  CWD in project mode (staging dir stays on PYTHONPATH for imports);
  drop stale 'sandboxed' framing from the intro and skill-passthrough
  paragraph.
- getting-started/learning-path.md: update the one-line Code Execution
  summary to match (no longer 'sandboxed environments' — the default
  runs in the session's real working directory).

No code changes.
@teknium1 teknium1 merged commit a2c9f5d into main Apr 18, 2026
4 of 5 checks passed
@teknium1 teknium1 deleted the hermes/execute-code-mode-docs branch April 18, 2026 08:53
cg2aigc pushed a commit to cg2aigc/hermes-agent that referenced this pull request Apr 18, 2026
@teknium1 @cg2aigc
docs(execute_code): document project/strict execution modes (NousRese…
a061eeb 
…arch#12073)

Follow-up to PR NousResearch#11971. Documents the new code_execution.mode config
key and what each mode actually does.

- user-guide/configuration.md: add mode: project to the yaml example,
  explain project vs strict and call out that security invariants are
  identical across modes.
- user-guide/features/code-execution.md: new 'Execution Mode' section
  with a comparison table and usage guidance; update the 'temporary
  directory' note so it reflects that script.py runs in the session
  CWD in project mode (staging dir stays on PYTHONPATH for imports);
  drop stale 'sandboxed' framing from the intro and skill-passthrough
  paragraph.
- getting-started/learning-path.md: update the one-line Code Execution
  summary to match (no longer 'sandboxed environments' — the default
  runs in the session's real working directory).

No code changes.
ulasbilgen pushed a commit to ulasbilgen/hermes-adhd-agent that referenced this pull request May 1, 2026
@teknium1
docs(execute_code): document project/strict execution modes (NousRese…
a228b33 
…arch#12073)

Follow-up to PR NousResearch#11971. Documents the new code_execution.mode config
key and what each mode actually does.

- user-guide/configuration.md: add mode: project to the yaml example,
  explain project vs strict and call out that security invariants are
  identical across modes.
- user-guide/features/code-execution.md: new 'Execution Mode' section
  with a comparison table and usage guidance; update the 'temporary
  directory' note so it reflects that script.py runs in the session
  CWD in project mode (staging dir stays on PYTHONPATH for imports);
  drop stale 'sandboxed' framing from the intro and skill-passthrough
  paragraph.
- getting-started/learning-path.md: update the one-line Code Execution
  summary to match (no longer 'sandboxed environments' — the default
  runs in the session's real working directory).

No code changes.
aj-nt pushed a commit to aj-nt/hermes-agent that referenced this pull request May 1, 2026
@teknium1
docs(execute_code): document project/strict execution modes (NousRese…
5e9b0ee 
…arch#12073)

Follow-up to PR NousResearch#11971. Documents the new code_execution.mode config
key and what each mode actually does.

- user-guide/configuration.md: add mode: project to the yaml example,
  explain project vs strict and call out that security invariants are
  identical across modes.
- user-guide/features/code-execution.md: new 'Execution Mode' section
  with a comparison table and usage guidance; update the 'temporary
  directory' note so it reflects that script.py runs in the session
  CWD in project mode (staging dir stays on PYTHONPATH for imports);
  drop stale 'sandboxed' framing from the intro and skill-passthrough
  paragraph.
- getting-started/learning-path.md: update the one-line Code Execution
  summary to match (no longer 'sandboxed environments' — the default
  runs in the session's real working directory).

No code changes.
02356abc pushed a commit to 02356abc/hermes-agent that referenced this pull request May 14, 2026
@teknium1
docs(execute_code): document project/strict execution modes (NousRese…
4e6c1d0 
…arch#12073)

Follow-up to PR NousResearch#11971. Documents the new code_execution.mode config
key and what each mode actually does.

- user-guide/configuration.md: add mode: project to the yaml example,
  explain project vs strict and call out that security invariants are
  identical across modes.
- user-guide/features/code-execution.md: new 'Execution Mode' section
  with a comparison table and usage guidance; update the 'temporary
  directory' note so it reflects that script.py runs in the session
  CWD in project mode (staging dir stays on PYTHONPATH for imports);
  drop stale 'sandboxed' framing from the intro and skill-passthrough
  paragraph.
- getting-started/learning-path.md: update the one-line Code Execution
  summary to match (no longer 'sandboxed environments' — the default
  runs in the session's real working directory).

No code changes.
gweeteve pushed a commit to gweeteve/hermes-agent that referenced this pull request Jun 2, 2026
@teknium1
docs(execute_code): document project/strict execution modes (NousRese…
e604007 
…arch#12073)

Follow-up to PR NousResearch#11971. Documents the new code_execution.mode config
key and what each mode actually does.

- user-guide/configuration.md: add mode: project to the yaml example,
  explain project vs strict and call out that security invariants are
  identical across modes.
- user-guide/features/code-execution.md: new 'Execution Mode' section
  with a comparison table and usage guidance; update the 'temporary
  directory' note so it reflects that script.py runs in the session
  CWD in project mode (staging dir stays on PYTHONPATH for imports);
  drop stale 'sandboxed' framing from the intro and skill-passthrough
  paragraph.
- getting-started/learning-path.md: update the one-line Code Execution
  summary to match (no longer 'sandboxed environments' — the default
  runs in the session's real working directory).

No code changes.
Egavasyug pushed a commit to Egavasyug/hermes-agent that referenced this pull request Jun 10, 2026
@teknium1
docs(execute_code): document project/strict execution modes (NousRese…
7393d63 
…arch#12073)

Follow-up to PR NousResearch#11971. Documents the new code_execution.mode config
key and what each mode actually does.

- user-guide/configuration.md: add mode: project to the yaml example,
  explain project vs strict and call out that security invariants are
  identical across modes.
- user-guide/features/code-execution.md: new 'Execution Mode' section
  with a comparison table and usage guidance; update the 'temporary
  directory' note so it reflects that script.py runs in the session
  CWD in project mode (staging dir stays on PYTHONPATH for imports);
  drop stale 'sandboxed' framing from the intro and skill-passthrough
  paragraph.
- getting-started/learning-path.md: update the one-line Code Execution
  summary to match (no longer 'sandboxed environments' — the default
  runs in the session's real working directory).

No code changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@teknium1