Practical Notes
The fastest evaluation loop is: install → hector serve → open Studio → run a toy agent prompt. Then add one real tool (MCP) and validate: permissions, logs, and failure modes. If you can’t explain the security boundary, you’re not ready to put it in front of production data.
Safety note: Self-hosting shifts responsibility to you. Define boundaries: network egress, secrets handling, and audit logs before onboarding real repos.
FAQ
Q: Is it only for local dev? A: No. It targets self-hosted deployments, including Docker-based runs.
Q: Do I need to be “all in” to try it? A: No. Start with one agent and one tool integration, then decide if it fits.
Q: How does MCP fit in? A: Use MCP as the tool layer; keep runtime policies and hosting in Hector.