Add AGENTS.md with Cursor Cloud dev environment instructions - #45
Draft
mikkelchokolate wants to merge 1 commit into
Draft
Add AGENTS.md with Cursor Cloud dev environment instructions#45mikkelchokolate wants to merge 1 commit into
mikkelchokolate wants to merge 1 commit into
Conversation
Co-authored-by: mikkelchokolate <mikkelchokolate@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Sets up and documents the Cloud Agent development environment for Veil, and adds an
AGENTS.mdwith a## Cursor Cloud specific instructionssection covering the toolchain, build/lint/test/run commands, and non-obvious gotchas.This PR only adds
AGENTS.md— no application code is changed. The environment update script is configured separately (via the environment settings), not in the repo.Environment setup performed
1.27.0(matchesgo.mod); Node26.7.0+ pnpm11.22.0(matchesweb/package.jsonpackageManager, Dockerfile, andscripts/ci/versions.sh). Node 26.7.0 installed vianvm(the runner injects a differentnodeat the front ofPATH, so it must be activated for frontend commands — documented inAGENTS.md).caddyv2.11.4 with theklzgrad/forwardproxymodule into/usr/local/bin/caddy, which theinternal/protocolsandinternal/protocols/naiveproxyGo tests require (they probecaddy list-modules --json).go mod download, thencorepack pnpm install --frozen-lockfileinweb/.Verification
corepack pnpm install --frozen-lockfilecorepack pnpm build(→web/dist)corepack pnpm typecheckcorepack pnpm check(Biome)corepack pnpm test(Vitest jsdom)corepack pnpm gen+ git diffcorepack pnpm i18n:checkgo build -o bin/veil ./cmd/veil(embedsweb/dist)go vet ./...go test ./...internal/protocols*oncecaddyis present)veil serve+ privileged helperHello-world demo
Ran the Panel end-to-end (privileged helper as root +
veil serveas theveiluser), created the initial administrator via the first-run setup, logged in, and used the authenticated Panel (Overview + Users showing theadminuser).veil_panel_clean_first_run_and_login_demo.mp4
Authenticated Veil Panel Overview dashboard
Veil Panel Users page listing the admin user
Note: the demo surfaced minor post-login/logout routing quirks in the app UI. These are existing application behaviors, unrelated to environment setup, and are out of scope for this PR.
To show artifacts inline, enable in settings.