docs(AGENTS): add Cursor Cloud environment setup instructions - #695
Draft
justrach wants to merge 1 commit into
Draft
docs(AGENTS): add Cursor Cloud environment setup instructions#695justrach wants to merge 1 commit into
justrach wants to merge 1 commit into
Conversation
Co-authored-by: Rach <justrach@users.noreply.github.com>
|
👋 Thanks for the contribution! Quick heads-up: this repo lands changes on the current Please retarget this PR via Edit → base branch to the active (Automated hint — reply here if you need a hand.) |
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.
Summary
Sets up the Cloud Agent development environment for this Zig codebase and records durable, non-obvious setup guidance in
AGENTS.md. No source code changed.The startup update script (registered separately, not committed) installs the exact pinned Zig dev snapshot
0.17.0-dev.813+2153f8143(frombuild.zig.zon/ release CI) to~/.local/zigand symlinks it ontoPATH. The vendorednanoregexis the only build dependency.What was verified
zig build→zig-out/bin/codedb(dev/debug).zig fmt --check srcruns. Exits non-zero only due to pre-existing formatting drift in ~6 tracked files (not introduced here).zig build test→ 981/982 pass. The one crash is a pre-existing Linux-only inotify bug insrc/watcher.zig(see below).scripts/e2e_mcp_test.py→ 53/54 pass (the lone failure is an unrelatedcodedb_indexMCP-tool assertion; all live-watch scenarios pass).codedb <root> tree|search|find|word) indexes 643 files and returns real structural/trigram/word-index results; themcpdaemon answerstools/callrequests.Pre-existing Linux daemon crash (documented, not fixed)
The
serve/mcpdaemons and watcher-exercising tests panic on Linux (watcher.zig"integer does not fit in destination type") when arming inotify against the sentinel path/tmp/codedb-notify. Root cause: the binary links libc, sostd.posix.errnouses libc semantics (only-1is an error), butstd.os.linux.inotify_add_watchreturns-errno;-ENOENTon the missing sentinel is misread as success and@intCastpanics. Maintainers develop on macOS (kqueue path), so this Linux path is currently unfixed onmain. Workaround for running daemons/E2E without touching source:: > /tmp/codedb-notify. This is documented inAGENTS.md.Notes
AGENTS.md## Cursor Cloud specific instructionscaptures the toolchain pin, build/lint/test/run commands, the Linux inotify gotcha + workaround, and the fact thate2e_mcp_test.pywrites temp projects into--project's parent (so run it from a writable-parent dir, not/workspace).codedb.snapshot(generated) was intentionally left unmodified.