Commit
28b8e9c
Done: PR #43 https://github.com/dtinth/agent-env/pull/43 . Docker detail now opens with a 'What it means for you' section in plain terms, with the five-flags note kept below it. Screenshot attached. vp check + 93 tests green. @dtinth
GitHubConfigurator: a plain-language Docker note by dtinth-claw[bot] · Pull Request #43 · dtinth/agent-envThe Docker detail in the "What runs" step opened straight onto the five host flags. For someone who isn't going to parse cap_add: SYS_ADMIN, that reads as noise. Adds a What it means ...
Oh, that's a huge wall of text. Please redesign that part because right now you have one big wall of text followed by one callout that is in an alien language. Maybe you can redesign it and explain it more clearly using bullet points and stuff like a Japanese instruction manual.
Redesigned, pushed to PR #43. Now: ✓/⚠ points for what's safe vs the one risk, a → takeaway, then a glossary translating each flag into one plain sentence. No more wall of text or alien block. Checked on desktop + phone. @dtinth
I think it can still be made more clear. Also, I think the black box is not necessary. Sometimes we will compare this to the --privileged flag. So, I would like you to make the list tell both what access does this flag enable and what was not granted that would be granted when…
Updated PR #43. Box gone; each flag now has Opens (what it grants) and Still shut (what --privileged would add but this doesn't), so the gap shows per flag. Screenshot attached. @dtinth
Then what it means for you. I think the text is still hard to understand. It would be great if you can rephrase it as ASDSTE100.
And for the next section, I think it should just list the flags. Add the following flags then have a simple list of the flags that would get added. No…
Done, PR #43 updated. Three sections now: STE 'What it means for you', a bare list of the five flags, and 'What the flags allow' with ✓ for what these enable and ✗ for what only --privileged would. Screenshot attached. @dtinth
Thanks merged
Thanks! Glad the Docker note landed. Cleaning up the worktree on my end. Shout if you want the same treatment on any other component's explainer.
Let's try that! Please run a web server at 0.0.0.0 and link me to it at http://box2:<port>/… so I can preview live.
Preview's live on port 5210 (bound to 0.0.0.0, at the address you gave). Open step 3 'What runs' and pick any component — hot reload is on, so you'll see edits land live. Which explainer first? SMB share's 'needs' note is the densest; or name another. @dtinth
Yeah try that.
SMB share is redone live — open step 3 'What runs' → SMB share on the preview. Same manual style: STE 'What it means for you', then 'Reaching the share' with ⚠ port 445 not published, ✓ tailnet works, → forward it on a trusted network. Not committed yet — tell me what to change.…
SMB:
- No need for "not published". It's too terse and confusing.
- "You browse, edit, add and remove the workspace files directly." > "The container runs a network drive." Also add notes about password.
- "Reaching the share" > This can be dynamic based on settings.
Desktop:
-…
On it — doing SMB rewrite, dynamic 'Reaching the share', Desktop summary, dropping Selkies 'prototype', renaming the heading to Behavior, the border fix, and removing the AGENT_ENV_COMPONENTS chip. One clarify: image 1 ('UI Scaling'/'Command sends Control') isn't the configurator…
I want Selkies backend's own scaling fixed on mobile
Selkies scaling fix done too: run-selkies now passes --scaling-dpi=96, which LOCKS it to 100% server-side (a single value means the client can't change it), so the phone no longer auto-picks 300%. Matches noVNC 1:1; DESKTOP_DPI still scales XFCE itself. Can't live-test without a…
yes please
Done — PR #44: https://github.com/dtinth/agent-env/pull/44 . Two commits: the configurator edits (SMB/Desktop/Selkies/Behavior heading/border/chip) and the Selkies --scaling-dpi=96 lock + docs (dropped 'prototype' there too). vp check + 93 tests green. Preview's still live if you…
GitHubConfigurator: plainer SMB/Desktop detail; pin Selkies UI scaling by dtinth-claw[bot] · Pull Request #44 · dtinth/agent-envFollows the Docker explainer (#43) with the same treatment for the other components, plus a Selkies mobile-scaling fix. Configurator SMB share — a Behavior list, and a Reaching the share section t...
Merged. For every component in the "What runs", let's remove the black box with "Shows up at" and "Needs". Replace with a behavior section.
commit 28b8e9c
On it — dropping the 'Shows up at / Needs' box from every component and giving each a Behavior section instead (Terminal, Files, OpenCode, Desktop; Docker and SMB already have one). I'll bring the live preview back up so you can watch.
Done — PR #45: https://github.com/dtinth/agent-env/pull/45 . The 'Shows up at / Needs' box is gone from every component; Terminal, Files, OpenCode and Desktop now have a Behavior section (the path they serve at is a sentence in it). Docker/SMB just lose the box. Live on the…
GitHubConfigurator: drop the facts box for a Behavior section on every component by dtinth-claw[bot] · Pull Request #45 · dtinth/agent-envRemoves the "Shows up at / Needs" box from every component in the "What runs" step and replaces it with a Behavior section, so every component reads the same way Docker and SMB ...