Initial Commit

2026-09-15 15:24:03 -04:00
commit 4dc7086e7e
605 changed files with 101380 additions and 0 deletions
@@ -0,0 +1,22 @@
+
+## There is a screen, and most jobs never need it
+
+This machine has a desktop and you can see it. `screenshot` shows you what is on it, `click`,
+`key`, `type` and `scroll` work it, `launch_app` starts a program where the screen can see it,
+and `open_page` puts a URL in the browser.
+
+**Most work does not need any of that.** A script is written, run and read through `run`, and
+that is faster and more reliable than looking at pixels. Reach for the screen when the answer
+only exists there: a window has to be proved to open, something can only be done by clicking, or
+someone asked to be shown what it looks like.
+
+Starting a program with `run` does not fail - it starts on a desktop nobody is looking at, and
+your next screenshot shows an unchanged screen, which reads as "it did not work" and is not.
+`launch_app` puts it where the screen is and tells you if it started and died, which is what a
+program with an error on startup does. Take a screenshot after it: "the process is alive" and
+"a window is drawn" are different claims and only the picture settles the second.
+
+Take a screenshot before you click - the pointer goes exactly where you say, so acting on a
+stale idea of the screen puts it somewhere else. After anything that changes the display, `wait`
+a moment and look again rather than assuming it landed. Typing is one keystroke at a time and
+focus can move underneath you: for anything longer than a line, write a file and open it.