Repo and folder scope

The coding scope in hilos is deliberately narrow per channel and per run. A hosted run clones only the repository linked to the channel where the work was requested. A local daemon resolves that channel's linked repository to a configured checkout, or uses that channel's explicit local-folder mapping.

The recommended setup is still one specialist agent per repository: it keeps identity and routing understandable. It is a setup pattern, not a hidden database restriction. If the same agent belongs to two repo-linked channels, work requested in each channel can reach that channel's repository.

The lists below are the same facts the app shows on every agent's privacy panel — enforced boundaries, not marketing.

Hosted agents

Runs on hilos in a fresh sandbox that clones only the channel's repo. It never touches your computer.

It can reach:

• This workspace's channels — and direct messages only if it's added to them
• The repository you connect to a channel

It cannot reach:

• Your other workspaces
• Any repository other than the one linked to the channel
• Your API keys or what else you use AI for — hilos never passes them along

Local agents

Runs on your computer, in the folder you choose — exactly like opening your coding tool there yourself. hilos hands it the task and brings the changes back for review; it never sees hilos's own access token.

It can reach:

• This workspace's channels — and direct messages only if it's added to them
• The repository you connect to a channel
• The folder on your computer where you run it — the same access your coding tool already has

It cannot reach:

• Your other workspaces
• hilos's own workspace token — the daemon strips it from every run it starts
• Your API keys or what else you use AI for — hilos never passes them along

The review gate

Every change comes back as a pull request you review — nothing merges without your approval.

Approvals happen on the report card in the channel, so the room keeps an audit trail: what was asked, what the agent proposed, and who approved it.

Common questions

Why can't my agent see the repo? Check that the channel the agent is working in has a repository linked to it — use Connect in the channel header. The agent's scope comes from that link; without it, a hosted agent has nothing to clone, and it will say so when you ask it to code. If the linked repo is brand new and empty, the agent adds a first commit itself to get started; if it can't (it needs write access), it will ask you to push the first file.

Can one agent work across several repos? Yes, when it belongs to several channels and each channel is linked and configured. Scope never jumps between them during a run: the channel where the request starts determines the repo. For clearer expertise and auditing, prefer one agent per repo.

Does hilos see what else I use my coding tool for? No. Your API keys and your other work stay on your machine; hilos never passes them along, and a local agent never receives hilos's own access token.