Skip to content

Set up Cloud Agent development environment #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bschellenberger2600 merged 1 commit into from
Jun 17, 2026
Merged

Set up Cloud Agent development environment #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,4 +27,19 @@ These notes apply to humans and to automated agents (including Cloud Agents).

---

## Cursor Cloud specific instructions

This repo is the `git-harness` Go library plus a CLI and polyglot (Python + Java) wrappers. Standard commands live in `README.md` and `.github/workflows/ci.yml`; only the non-obvious cloud caveats are noted here.

**Layers**
- Go core (`git/`, `safety/`): `go build ./...`, `go vet ./...`, `go test -race -count=1 ./...` (see `README.md`).
- CLI (`cmd/git-harness-cli`): a stdin/stdout JSON bridge. Build with `go build -o ./bin/git-harness-cli ./cmd/git-harness-cli`.
- Wrappers (`testkit/python`, `testkit/java`): both shell out to the CLI and require `GIT_HARNESS_CLI` to point at the built binary (e.g. `export GIT_HARNESS_CLI=/workspace/bin/git-harness-cli`). Build the CLI first.

**Python wrapper**: Ubuntu is PEP 668 managed, so deps live in a dedicated venv at `~/.venvs/git-harness` (created by the update script). Run tests/samples with that interpreter, from `testkit/python`: `"$HOME/.venvs/git-harness/bin/python" -m pytest tests/ -q` and `-m samples.smoke_repo_flow` / `-m samples.smoke_safety_flow`. Note CI calls bare `python`, but only `python3` exists here.

**Java wrapper**: needs Maven + JDK 21 (baked into the snapshot). From `testkit/java`: `mvn test`, and samples via `mvn -Dtest=SampleRepoFlowSmoke,SampleSafetyFlowSmoke test`. First run populates the `~/.m2` cache.

**Known cloud-only test failure**: `git/command_test.go::TestFetchRemote_UnauthenticatedHTTPSFailsWithoutPrompt` fails in this environment. The cloud agent configures a global `url.https://x-access-token:<token>@github.com/.insteadOf` rewrite, so the "unauthenticated" fetch is actually authenticated and GitHub returns `Repository not found` instead of the expected credential-prompt error. This is an environment artifact, not a code bug; it passes in clean CI. Skip it with `-skip 'TestFetchRemote_UnauthenticatedHTTPSFailsWithoutPrompt'` when validating locally.


Loading