Workspace context and environments
Set the company background every agent receives, keep team secrets out of prompts, and choose the ports used for sandbox previews.
Workspace context gives every agent the same company facts. Team environment variables hold secret runtime values, while environment settings decide which local app ports receive preview URLs.
Give every agent a common starting point
Admins set the workspace name, logo, website, and company context in General settings. Hivy adds the name, website, and company context to each agent's runtime instructions.
Company context should answer four questions
- What does the company make or operate?
- Who does it serve?
- Which terms, products, and boundaries recur in the work?
- How should agents write when they represent the company?
The website field adds a reference to the prompt; it does not crawl or index the site. Add a website knowledge source when agents need to search its pages.
Video placeholder
Update the demo workspace context, add a described environment variable to one team, then start a session and show the agent recognizing the variable name without revealing its value.
Keep secret values with the team
Open a team in Settings, then add an environment variable with a name, value, and useful description. Hivy encrypts the value and never returns it to the settings page after saving.
Sessions for that team receive the variable in their sandbox. The agent can see the name and description in its context, but its instructions forbid reading, printing, logging, or storing the value.
Image placeholder
Capture one team with two demo variables. Show useful descriptions and masked saved values; never use a real secret.
Expose only the preview ports you use
Environments settings controls the local ports Hivy exposes through public sandbox preview URLs. The default list covers 3000, 5173, 8000, and 8080; admins can save up to 20 distinct ports between 1 and 65535.
Port 7080 belongs to the Hivy runtime and cannot be selected. A port change applies only to new sandboxes, so recreate an existing sandbox before expecting a new preview route.
Put each kind of context in the right place
- Workspace context holds short company facts every agent needs.
- Knowledge sources hold indexed material that selected teams can search.
- Environment variables hold encrypted values used by programs and tools inside one team's sessions.
- Skills hold reusable methods, never credentials.