Agent environment

How do I use the Hermes Hub agent environment?

Use the Hermes Hub agent environment by keeping durable tenant artifacts in the private workspace, treating company storage as shared input when granted, and using the documented environment keys for tenant identity and runtime access. Keep credentials, private browser state, and runtime software under the tenant runtime boundary rather than shared storage.

The main environment boundaries

Use each path for its documented purpose.

Private workspace

Store reports, datasets, builds, and other durable artifacts visible to the tenant.

Company storage

Use shared company or team content only when the tenant has the appropriate grant.

Runtime state

Keep credentials, browser state, skills, cron configuration, and caches in operator-managed runtime locations.

Environment references

Hermes Hub agent environment FAQ

What belongs in the tenant workspace?
Reports, images, generated documents, datasets, build outputs, and other durable tenant-visible artifacts belong in the workspace.
Can private secrets be placed in company storage?
No. Treat company storage as shared input and keep secrets, private browser state, and private runtime memory out of it.
What does the browser variable mean?
When browser support is enabled, the browser endpoint and profile are tenant-private runtime resources and should not be copied into shared storage.

Design a tenant environment

Discuss workspace, company storage, runtime, browser, skill, and cron boundaries for Hermes Hub.

+1 332 2081410
[email protected]

Architecture conversation

Tell us what your team needs to control

Share your deployment boundary, number of agents, work surfaces, and governance requirements. We will reply by email to arrange a focused technical discussion.

Email the Bewize team

This opens your email application. Read our Privacy Policy.