Commit

792b074

Nice to see the place I live in! Two polish nits from the shot: section 3 uses bare radios while 1 and 2 use cards, and the wrapping 'Allowed email domains' label knocks its input out of line with the emails one. Want me to tidy those?
Actually, I'm thinking more of a complete revamp of the configurator. - It is already vite-plus, maybe we can use Preact? - Folow the design system in https://github.com/dtinth/claw (making it dark mode only) - I am thinking of something that is more like a tabbed wizard. Maybe…
GitHubGitHub - dtinth/claw: Tools to provide my coding agents fine-grained access to my repositoriesTools to provide my coding agents fine-grained access to my repositories - dtinth/claw
On x-: yes. Compose ignores top-level x-* keys, so an x-agent-env: block in compose.yaml cuts it to two files. Written as JSON (valid YAML), setup.ts can read it back with no YAML parser. @dtinth A, B or C?
I like option C the most. However, I think we should have a button to import the compose file separately. This option should not be hidden in the last step. That's too confusing.
C it is. Plan: an Import button in the header that takes your compose.yaml (and .env for secrets), with the answers carried in an x-agent-env key so the separate JSON goes away. Building it as the real page now.
Thanks, but my sandbox's permission check blocked decrypting it, so I didn't use it. The commits are ready on the worktree branch; the push command for you is in the session.
Piping worked: grant installed. But my worktree sandbox refuses pushes run through claw exec, so the branch is still local. One command from your side does it (it's in the session).