Commit
96cc35c
Great. Writing the component system doc now, then the Haiku review loop. Will post the result here.
@dtinth The component system doc is ready, revised over 3 rounds of Haiku review (fresh reviewer each time, reading only that file, flagging confusion and internals):
https://github.com/dtinth/agent-env/blob/components-doc/docs/components.md
Things I decided while writing it,…
GitHubagent-env/docs/components.md at components-doc · dtinth/agent-envhttps://dtinth.github.io/agent-env/. Contribute to dtinth/agent-env development by creating an account on GitHub.
Reviewing.
Give it a provider API key (such as ANTHROPIC_API_KEY) in your compose file, or sign in from its UI.No need - just
/connect from UI.
For smb, auto-generate a password if none set?Both done in https://github.com/dtinth/agent-env/commit/5e36345: opencode row now just says /connect. smb generates a password on first start and keeps it (SMB_PASSWORD overrides); user dev, and the password plus the smb:// address show on the /~env/ page. Off a tailnet, the…
GitHubdocs: components — opencode via /connect, smb generates its password · dtinth/agent-env@5e36345Co-authored-by: Thai Pangsakulyanont <193136+dtinth@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Good. Let’s implement this. Make a PR and shepherd it.
On it. This is a big one (entrypoint, gateway, agent-env CLI, presets to components, configurator, smoke tests), so expect a while. I'll post the PR link when it's up and green.
Pls also re-read the dev-null-bridge skill, esp. re. the part about traceability.
Re-read. I'd missed Traceability. From now on every commit gets Requested-in: trailers for the dev-null commits behind it, and the PR body links them. The two doc commits already pushed lack them; the PR description will cover those rather than force-pushing.
PR is up: https://github.com/dtinth/agent-env/pull/41 (passes locally: 98/100/92 smoke). Waiting on CI and review now; I'll tag you when it's green.
GitHubComponents: replace presets and the *_ENABLE flags by dtinth-claw[bot] · Pull Request #41 · dtinth/agent-envPresets and the *_ENABLE flags are replaced by components. A component is a folder with an agent-env-component.toml, plus whichever of pitchfork.toml, mise.toml, env.sh and bin/ it needs. The user ...
@dtinth https://github.com/dtinth/agent-env/pull/41 is green. I fixed all 6 Devin findings in 53b304c; draft replies are in the session for you to post.
GitHubComponents: replace presets and the *_ENABLE flags by dtinth-claw[bot] · Pull Request #41 · dtinth/agent-envPresets and the *_ENABLE flags are replaced by components. A component is a folder with an agent-env-component.toml, plus whichever of pitchfork.toml, mise.toml, env.sh and bin/ it needs. The user ...
You can reply directly
Done, all 6 replies are on the PR, e.g. https://github.com/dtinth/agent-env/pull/41#discussion_r4366975565. Noted for next time: I'll reply to review bots myself.
GitHubComponents: replace presets and the *_ENABLE flags by dtinth-claw[bot] · Pull Request #41 · dtinth/agent-envPresets and the *_ENABLE flags are replaced by components. A component is a folder with an agent-env-component.toml, plus whichever of pitchfork.toml, mise.toml, env.sh and bin/ it needs. The user ...
Do you have screenshots of the new configurator?
Yes, from the PR branch. Step 3 "What runs": OpenCode at /, one desktop choice, then extras. SMB only shows on a tailnet (2nd). It always writes AGENT_ENV_COMPONENTS (3rd).
I would like to revamp this configuration so it is more modular. Can you prototype a few UI examples so I can choose from it? Also, where can I configure the provisioning script?
@dtinth 3 takes on "What runs": A catalog cards, B list+detail, C chips + boot timeline. All add git-repo components and a startup script as compose configs (mock for now). Branch components-ui-protos: https://github.com/dtinth/agent-env/commit/276bff3. Which one?
GitHubConfigurator prototypes: three takes on a modular What runs step · dtinth/agent-env@276bff3For choosing a direction. Each is its own page under vp dev (/proto-a.html, /proto-b.html, /proto-c.html, ?demo=ready for a full one) and replaces only step 3 of the real stepper: - A, catalog: co...
I like number two the most, but can you show me how it might look like on mobile? Also, let's add the SMB server here.
@dtinth B on a phone: list first, tap opens the detail with a back link, switches work from the list. SMB is now always listed; off a tailnet it's disabled and says why. Is that what you meant by adding SMB? https://github.com/dtinth/agent-env/commit/13738e1
GitHubPrototype B: a phone layout, and SMB always listed · dtinth/agent-env@13738e1Under 700px the list and the detail take turns: the list fills the step, picking an item opens its detail with a back link, and the switches still work from the list. SMB is listed in every mode. ...
I think we don't need the switch inside the list. Just go to the details and switch it on or off because currently it is not clear when you configure that you can go inside and adjust it.
Furthermore, I think it is fine to have SMB on non-Tailnet setup because each compose…
@dtinth Done: the list only shows On/Off and a ›, the switch lives in the detail. SMB is offered in every mode now, never published; off a tailnet it says to forward 445 yourself. That's in PR #41 too (0dc7371). Protos: https://github.com/dtinth/agent-env/commit/bd45739
GitHubPrototype B: no switches in the list; SMB offered in every mode · dtinth/agent-env@bd45739The list only shows each item's state (On, Off) and a chevron, so it reads as something to open; turning a component on or off is done in its detail. SMB follows the configurator: offered in ev...
commit 96cc35c
On mobile, the stepper looks off because the step number circles wrap into the second line.
For the your own app, I'm not sure if this is needed because now we can just create components on our own and we already have the provisioning script and stuff like that. Personally, I…