# Tips for ChromeOS / Chromebook

## Chrome Applications

* [Clipboard Manager](https://chrome.google.com/webstore/detail/clipboard-manager/hlmagkbphobghocaimgijjjpmionjcnj/)
* [txt.app Text editor](https://chrome.google.com/webstore/detail/text/mmfbcljfglbokpmkimbfghdkjmjhdgbg)
* [SSH/scp](https://chrome.google.com/webstore/detail/secure-shell-app/pnhechapfaindjhompbnflcldabbghjo?hl=en-US)
* [BeagleTerm Serial terminal](https://chrome.google.com/webstore/detail/beagle-term/gkdofhllgfohlddimiiildbgoggdpoea) for working with embedded devices
* [Chrome ADB Client (Android Debug Bridge)](https://chrome.google.com/webstore/detail/chromeadb/fhdoijgfljahinnpbolfdimpcfoicmnm) for developer/debug stuff with Android devices
* [Insomnia REST client](https://chrome.google.com/webstore/detail/insomnia-rest-client/gmodihnfibbjdecbanmpmbmeffnmloel)

## Google Chrome Labs at GitHub

<https://github.com/GoogleChromeLabs>

## Keyboard shortcuts

* Launch anything pinned to the dock `Alt + [1-9]`, where 1-9 is the position of an app within the dock, and position 1 is far left Ex: Alt + 2 starts/opens the 2nd app from the left in the dock
* Screenshots

`Ctrl + F5/Expose` == Entire screen

`Ctrl + Shift + F5/Expose` == Selected area

* Emulate keys not on keyboard

```
Use keys on top row:
F1 = search + "<--"
..
F10 = search + volume up
Delete = search + backspace
```

## Create folders in launcher

Drag one app onto another to create a new folder

## Using LXC commands to interact with containers

1. Start crosh
2. run `vmc start termina`

### Container actions

* `lxc list` - display installed containers and their current state
* `lxc image list` - container image, size, description, etc

## Advanced config settings

### Change build/channel

To switch to "beta" or "developer" channels to get new features early, but sacrificing some stability

```
### Enable Linux
Settings --> Linux --> Enable

Provides a Debian-based distro, using standard 'apt' tools


### Change Chrome download folder to be in your Google Drive
Settings --> Advanced --> Downloads --> Location


### URLs for hidden/advanced config options
```

chrome://chrom-urls - full list of supported urls

chrome://bluetooth-internals/ - advanced bluetooth details not available from Settings

chrome://components/ - most impt app to update: cros-termina

chrome://device-log/

chrome://devices

chrome://discards/ - not exactly sure what this is

chrome://drive-internals/ - Google Drive connection status, paths, event logs

chrome://flags - Enable hidden/beta features

chrome://gcm-internals/ - ??

chrome://gpu/ - detailed stats on GPU features, settings, logs, etc

chrome://inspect - Inspect pages, extensions, apps; dedicated DevTools for NodeJS

chrome://internet-config-dialog/ - shortcut to join a hidden wifi network

chrome://internet-detail-dialog/ - shortcut to proxy setting

chrome://interstitials/ - a list and example of all screens that Chrome sends you to in order to warn you before proceeding

chrome://interventions-internals/ - ?

chrome://local-state/ - JSON format of several metrics

chrome://net-export/ - Capture a network log, optionally including credentials

chrome://network/ - Visible wifi networks, plus other stuff I'm not sure what it does

chrome://omnibox/ - search box on steroids

chrome://power/ --- Battery usage graph!

chrome://predictors/ - list of predictions that Chrome will offer as you type, based on what it's learned from your browsing history

\`\`\`


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.ch1x0r.org/chromeos.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.