The g1t CLI is 0.3.5 and trusts the system's certificate store: in a Claude Managed Agents sandbox, which re-signs HTTPS with a proxy certificate it adds to /etc/ssl/certs, every g1t command failed TLS verification (the CLI trusted only the webpki-roots list built into it), so sessions gave up on the CLI and fell back to MCP tools and plain git ("The CLI can't verify the sandbox's TLS proxy"). ureq now has native-certs, as g1t-runner already does for guarded sandboxes. The CLI guide says so under Behind a TLS proxy. Checked: cargo test -p g1t (109 and 51). · 25309b9 · flagon-io/g1t

97	97
98	98		`g1t --version` prints the version you have.
99	99
	100	+	### Behind a TLS proxy
	101	+
	102	+	From 0.3.5 on, g1t trusts the certificates in your system's store, as
	103	+	curl and git do. A sandbox or corporate network that inspects HTTPS (a
	104	+	Claude Managed Agents sandbox, a guarded runner) adds its proxy's
	105	+	certificate there, so g1t works through it with nothing to set. Earlier
	106	+	versions trusted only a list built into the CLI and refused such a proxy.
	107	+
100	108		## Sign in
101	109
102	110		```sh

1	1		[package]
2	2		name = "g1t"
3		−	version = "0.3.4"
	3	+	version = "0.3.5"
4	4		edition.workspace = true
5	5		license.workspace = true
6	6		repository.workspace = true
⋯
28	28		sha2 = "0.10"
29	29		tar = { version = "0.4", default-features = false }
30	30		terminal_size = "0.4"
31		−	ureq = { version = "2", default-features = false, features = ["tls"] }
	31	+	# native-certs: sandboxes that re-sign HTTPS (Claude Managed Agents, guarded
	32	+	# runners) add their proxy's certificate to the system store, which the
	33	+	# webpki-roots bundle never sees.
	34	+	ureq = { version = "2", default-features = false, features = ["tls", "native-certs"] }
32	35

flagon-io/g1t