replying to @dtinth
Next: what goes in agent-env-component.toml. My proposal, smb as the example:…
Commit
ee9c7ac
Agree. The host is good. For mise tools, on reconcile, it would symlink the tool to conf.d right? e.g.
conf.d/agent-env-<name>.toml. And also deletes the ones not listed?Yes, symlink rather than copy (today it copies), so editing a component's mise.toml applies on the next
mise install. Tested: mise reads a conf.d symlink pointing outside ~/.config with no trust prompt, [env] included.
Deleting: the reconciler owns every…Looks good. Why we need
agent-env opencode in the first place? What is it for, like what are its use cases? No need to keep backwards compatibility tho.
Btw just noting, before you start the implementation I want you to make a docs describing the component system. Then, have a…Good question. Looking at them, there's not much case for it:
-
agent-env tui cds to the workspace, waits for the server and runs opencode --server .... But env.sh already sets OPENCODE_SERVER and its password in login shells, so plain opencode attaches to the same server.…Why not add
bin/ to PATH?We could. Links into ~/.local/bin win on two points:
- Instant: ~/.local/bin is already on PATH everywhere (login shells,
ssh box cmd, daemons, open terminals). A new PATH entry only reaches shells and daemons started after install, and /etc/environment would need rewriting as…How about ~/.agent-env/bin in PATH?
By the way, for the sub-agent review, I want it to also flag the implementation details they did not need to know so the docs is user facing.
Another question is what language would you use to implement these commands? Python?
~/.agent-env/bin: yes, that's the best of both. It's a fixed entry, so it goes on PATH once at boot (profile.d + /etc/environment) and reaches everything. Install drops links into it, so commands are live immediately and clashes are caught. Then why not put components there too,…
Last open branch before I write the doc: defaults.
Today, with nothing set, you get the desktop, terminal and file manager, and opt in to opencode and docker. As components, I'd make the default AGENT_ENV_COMPONENTS=desktop,terminal,files. Setting the variable replaces that list…
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 ...
commit ee9c7ac
@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 ...