Your computer has no internet access unless the workspace allows some. Internet access decides what the assistant's commands on it can reach, such as installing a Python or npm package, cloning a repository or downloading a file.
Where to find it
- Personal workspace: open Manage workspace → Settings → Your computer → Internet access. You choose for your own computer there.
- Shared workspace: open Workspace → Settings → Your computer → Internet access. The owner and admins choose for every member's computer in the workspace. Members see the setting and what it allows, but cannot change it; the page says so.
- On the phone: Manage workspace → Your computer → Internet access.
Each workspace has its own setting. Your computer in one workspace never follows another workspace's choice.
If you do not see Internet access, it is not available yet, and your computer has no internet access.
The four choices
- Off: no internet access. Artifacts reach the computer and leave it through Bluedeer only. This is where every workspace starts.
- Only listed sites: the computer reaches only the sites and groups on the Allowed sites list. Everything else is refused.
- All except listed sites: the computer reaches every site except the ones on the Blocked sites list.
- Allow all: the computer reaches every website.
Both lists are kept when you switch between choices, so you can go back without typing them again. Choose, then select Save.
Adding sites and groups
- Type a site's name, such as
example.com, and select Add. You can add several at once, separated by spaces or commas. If you paste an address such ashttps://example.com/page, only the name is kept. - A name covers the site and every name under it:
example.comalso coverswww.example.comandapi.example.com. To cover only the names under it, type*.example.com. - A group adds a set of sites in one click and shows as one item you can remove:
- Software packages: the package registries and their download servers, for example npm, PyPI, crates.io, Go modules, Maven Central, RubyGems, NuGet, Packagist, conda, CRAN, the Ubuntu, Debian and Alpine mirrors, Homebrew, Docker Hub and other container registries.
- Code hosting: GitHub (with its raw files and release downloads), GitLab and Bitbucket.
- IP addresses, one-word names such as
localhost, and local names cannot be added. If an entry cannot be used, the page says why next to it.
What stays the same in every choice
- Only secure websites (HTTPS) can be reached. Plain
http://addresses, email, SSH and other kinds of connection are always refused, so cloning a repository works with anhttps://address but not withgit@. - Private and local network addresses, and the addresses a cloud server uses for its own settings, are always refused, also with Allow all.
- Downloads and uploads have a daily limit per person, and a computer that tries a great many sites in a short time is stopped.
- Bluedeer's own file transfers do not depend on this setting: the assistant can always copy your artifacts to the computer and save results to your File manager.
When a change takes effect
A change applies straight away: computers that are running take it at once, and every command after that follows it. A download from a site that the new setting refuses is stopped.
What the assistant is told
The assistant knows which choice applies, but not the list itself. When it tries a site that the setting refuses, it is told that the site is blocked by the workspace's internet setting and who can change it, so it does not keep trying. It then tells you.
Things to know before allowing sites
The assistant reads what it fetches. A web page or a file from the internet can contain instructions written to mislead an assistant, for example to send out what is on the computer. Allow only the sites the work needs, and prefer Only listed sites with a group over Allow all.
In a shared workspace, each change is recorded in the workspace's Activity: who changed it, the choice, and the sites and groups added or removed.