Upload folder using huggingface_hub

.env.example

@@ -18,3 +18,6 @@ SSH_PRIVATE_KEY=
 SSH_PUBLIC_KEY=
 SSH_KNOWN_HOSTS=
 
+# Optional: Provider CLI auth (prefer env vars, not files)
+GEMINI_API_KEY=
+ANTHROPIC_API_KEY=

AGENTS.md

@@ -44,6 +44,7 @@ uvicorn main:app --reload --host 0.0.0.0 --port 7860
 - High-risk features are gated by Supabase auth and flags (`ENABLE_TERMINAL`, `ENABLE_CODEX`, `ENABLE_MCP`, `ENABLE_INDEXING`). Keep defaults conservative and document changes in `SECURITY.md`.
 
 ## Deployment notes (HF Spaces)
+
 - Port: `7860`
 - Persistence: `/data` is used for `~/.codex`, `~/.ssh`, and a default workspace directory when available.
 - Web terminals often require device auth flows; avoid localhost callback assumptions.

PLANS.md

@@ -70,6 +70,8 @@ This file is the repo-level roadmap for `autonomy-labs`. It’s intentionally op
   - GitHub repo indexing (branch/path filters, token support via Secrets)
 - Build a jobs UI: progress, retries, errors, and access controls.
 
+Note: see `docs/PASSWORD_MANAGER_SCOPE.md` for the current (non-vault) stance and recommended path forward.
+
 ## P3 — P2P pubsub chat + account manager
 - Implement account manager concepts:
   - identities/devices, room/topic membership, permissions, moderation tools
@@ -84,4 +86,3 @@ This file is the repo-level roadmap for `autonomy-labs`. It’s intentionally op
 - Add lint/tests + CI:
   - Python: `ruff`, `pytest`
   - basic security smoke tests for endpoint gating
-

TASKS.md

@@ -27,8 +27,8 @@ Legend:
 
 ## P2 — Provider auth parity (Codex/Gemini/Claude)
 - [x] Codex auth file generation from env/secrets (`~/.codex/.auth.json` and `~/.codex/auth.json`).
-- [ ] Gemini auth file parity (only if CLI requires; otherwise env-only with docs).
-- [ ] Claude auth file parity (only if CLI requires; otherwise env-only with docs).
+- [x] Gemini auth (env-only via `GEMINI_API_KEY`, documented).
+- [x] Claude auth (env-only via `ANTHROPIC_API_KEY`, documented).
 - [x] Optional SSH key support via Secrets (`SSH_PRIVATE_KEY`, `SSH_PUBLIC_KEY`, `SSH_KNOWN_HOSTS`).
 
 ## P2 — Codex workspace directory (UI)
@@ -49,7 +49,7 @@ Legend:
 - [x] Import/export `mcp.json` via UI with validation.
 
 ## P3 — RAG + indexing (docs/web/GitHub) + “password manager”
-- [ ] Clarify “password manager” scope and threat model.
+- [x] Clarify “password manager” scope and threat model (`docs/PASSWORD_MANAGER_SCOPE.md`).
 - [x] Document upload indexing connector (MVP: text-only, keyword search).
 - [ ] Website crawler indexing (depth/allowlist/robots/rate limits).
 - [ ] GitHub repo indexing connector (branch/path filters + token support).

docs/PASSWORD_MANAGER_SCOPE.md

@@ -0,0 +1,27 @@
+# “Password manager” scope (clarification)
+
+This repo currently **does not implement a password manager / secure vault**.
+
+## Why this matters
+
+A real password manager is a high-risk feature. To do it safely you need:
+- client-side encryption (or a trusted enclave) and a clear key-derivation strategy
+- strict access controls and auditing
+- safe handling of backups/exports
+- threat modeling for the deployment environment (HF Spaces, browser clients, admin operators)
+
+## What we can safely support first (recommended)
+
+**Indexed private notes / secrets references** (lower risk than storing raw credentials):
+- store *non-sensitive* snippets and references (e.g., “service X uses token Y stored in HF secret Z”)
+- use the existing RAG indexing pipeline for retrieval
+- keep actual secrets in HF Spaces Secrets or Supabase (never in git)
+
+## If you want a real vault
+
+We should treat it as a separate milestone:
+1. Define threat model (who can read, what happens if admin/host is compromised).
+2. Choose encryption strategy (client-side keys vs server-managed keys).
+3. Add UX for create/unlock/lock, rotate keys, and recovery.
+4. Add audit logging, rate limiting, and tests.
+

docs/TROUBLESHOOTING.md

@@ -19,6 +19,12 @@ If you use env-based token auth, set one of:
 Notes:
 - You do not need to provide `last_refresh` as a Secret; it is written automatically.
 
+## Gemini / Claude CLI authentication
+
+This repo prefers env-based auth for provider CLIs (keep tokens out of git and UI):
+- Gemini: `GEMINI_API_KEY`
+- Claude: `ANTHROPIC_API_KEY`
+
 ## RAG endpoints return 403 (“Indexing is disabled”)
 
 Set `ENABLE_INDEXING=1` in your environment and restart the container.