sliccy 6.156.0 → 6.157.0

package/README.md

@@ -49,7 +49,7 @@ and command coverage.
 ## Why SLICC is different
 
 - **Browser-native, not browser-adjacent.** The agent runtime lives in the browser, and the agent can act on the same browser it lives in. A great mix of power and containment. If you don't like what the AI does, close the browser tab and it's over.
-- **A real shell environment.** Many browser agents are constrained by the tools provided to them. SLICC has an almost-too-real shell with commands like `git`, "`node`", `python`, `playwright`, built-in.
+- **A real shell environment.** Many browser agents are constrained by the tools provided to them. SLICC has an almost-too-real shell with commands like `git`, "`node`", `python`, `playwright`, built-in. Text files use UTF-8 by default; binary pipelines and explicit file encodings preserve their bytes.
 - **UI on the fly.** SLICC can generate rich user interfaces on the fly. These can be small visualizations in a chat response, or full-blown web applications that run in a sidebar, or even a separate tab.
 - **Built around Skills.** Agents don't suffer from missing capabilities, they suffer from skill issues. SLICC can install native skills into `/workspace/skills`, and it also discovers compatible `.agents` / `.claude` skills read-only across the reachable VFS.
 - **More than a coding panel.** Coding is one strong use case, but SLICC is built for practical browser work too: authenticated web apps, repetitive tab work, content operations, debugging, research, and automation.
@@ -171,6 +171,26 @@ This finds the newest release carrying CLI binaries (they only attach when the C
 
 On macOS, launching a terminal follower from Sliccstart also exposes its managed CLI at `~/.local/bin/slicc`. Existing user installs are never replaced, and failure to create the symlink does not block the terminal launch.
 
+### 8. GitHub Actions
+
+Run a leader on a GitHub Actions runner for as long as a job allows, seed it with credentials, files, and mounted folders, and talk to it from the same job or from other workflows through the `slicc` CLI:
+
+```yaml
+jobs:
+  slicc:
+    uses: ai-ecoverse/slicc/.github/workflows/slicc-leader.yml@main
+    with:
+      duration: 45m
+      prompt: Summarize /mnt/repo/README.md into /workspace/summary.md
+      fetch-file: /workspace/summary.md
+      mounts: |
+        ${{ github.workspace }}:/mnt/repo
+    secrets:
+      SLICC_CONE_CONFIG: ${{ secrets.SLICC_CONE_CONFIG }}
+```
+
+Companion workflows send prompts, run shell commands, read and write VFS files, and lend a second runner to the leader as an exec-capable follower. Reference and recipes: [packages/github-workflow/README.md](packages/github-workflow/README.md).
+
 ## How it works
 
 SLICC shares one core across every runtime ("float"). The browser is not just where you view the product — it is where the agent runtime lives.
@@ -284,6 +304,9 @@ SLICC would not have been possible without the pioneering inspiration of [OpenCl
 
 ## Development and deeper docs
 
+Developers can verify native browser storage with `npm run test:opfs` and trial the
+[optional OPFS preload setting](docs/filesystem-preload.md).
+
 If you want to go deeper, the detailed docs live here:
 
 - [Development guide](docs/development.md)