Set up Cloud Agent development environment

[bschellenberger2600]

Summary

Sets up and verifies the full development environment for git-harness (Go library + CLI + Python/Java polyglot wrappers) for Cursor Cloud Agents.

The only code change is documentation: a new ## Cursor Cloud specific instructions section in AGENTS.md capturing the layer layout, the Python venv location, the GIT_HARNESS_CLI requirement for wrappers, and a known cloud-only test caveat.

Environment setup

• System deps installed during setup (baked into snapshot): python3.12-venv, maven (JDK 21 already present).
• Update script (refresh only): go mod download; create/refresh venv at ~/.venvs/git-harness; pip install -e "testkit/python[dev]".

Verification

Layer	Commands	Result
Go core	gofmt -l, go build ./..., go vet ./..., go test -race ./...	pass*
CLI	go build -o bin/git-harness-cli ./cmd/git-harness-cli + JSON smoke	pass
Python wrapper	pytest tests/ (10 passed) + 2 sample smokes	pass
Java wrapper	mvn test (4) + 2 sample smokes	pass
spec-kit	validate_specify.sh	pass

* One test, git/command_test.go::TestFetchRemote_UnauthenticatedHTTPSFailsWithoutPrompt, fails only in the cloud environment because the agent's global url.<token>.insteadOf rewrite authenticates the "unauthenticated" fetch (GitHub returns Repository not found instead of a credential prompt). This is an environment artifact, not a code bug; documented in AGENTS.md.

Hello-world (CLI end-to-end)

Detect dirty repo → git_auto_commit_dirty → verify clean → read branch/HEAD sha.

git_harness_hello_world.log
git_harness_env_verification.log

  

[coderabbitai]

Warning

Review limit reached

@bschellenberger2600, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 57 minutes and 29 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0ce7f2d8-9085-42c7-8b49-75e7b33a298a

📥 Commits

Reviewing files that changed from the base of the PR and between 34d1bcc and 267d74e.

📒 Files selected for processing (1)

• AGENTS.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/setup-dev-environment-00bd

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}