mawkone 229987e788 fix: use service account JSON key for Vertex AI auth instead of metadata server ...

The VM's metadata server doesn't grant cloud-platform scope by default.
Read GOOGLE_APPLICATION_CREDENTIALS_JSON env var (service account key JSON)
and pass it directly to GoogleAuth. Falls back to metadata server if unset.
This restores GLM-5 access via Vertex AI.

Made-with: Cursor

2026-02-27 19:51:48 -08:00

dist

fix: use service account JSON key for Vertex AI auth instead of metadata server

2026-02-27 19:51:48 -08:00

node_modules

init: vibn-agent-runner — Gemini autonomous agent backend

2026-02-26 14:50:20 -08:00

src

fix: use service account JSON key for Vertex AI auth instead of metadata server

2026-02-27 19:51:48 -08:00

.env.example

fix: add all missing source files (llm.ts, updated agent-runner/agents)

2026-02-27 19:33:59 -08:00

Dockerfile

fix: force NODE_ENV=development during npm ci so tsc is installed

2026-02-27 19:30:40 -08:00

package-lock.json

fix: replace gcloud shell-out with google-auth-library for Vertex AI tokens

2026-02-27 19:38:07 -08:00

package.json

fix: replace gcloud shell-out with google-auth-library for Vertex AI tokens

2026-02-27 19:38:07 -08:00

PROJECT.md

feat: Add GET /api/status endpoint with job stats and update PROJECT.md

2026-02-26 23:30:15 +00:00

tsconfig.json

init: vibn-agent-runner — Gemini autonomous agent backend

2026-02-26 14:50:20 -08:00

Description

No description provided

9.7 MiB

Languages

TypeScript 99.1%

Dockerfile 0.9%