Address code review

Author: igor0

examples/typescript-sdk/context/file-search-server/README.md

@@ -1,18 +1,18 @@
 # File Search Server Example
 
-REST API for semantic file search with AI-powered summarization and code explanation.
+REST API for semantic file search with AI-powered summarization.
 
 ## Prerequisites
 
-Install the `auggie` CLI:
+Install the `auggie` CLI and authenticate:
 ```bash
-auggie --version
+npm install -g @augmentcode/auggie
+auggie login
 ```
 
 ## Usage
 
 ```bash
-export AUGMENT_API_TOKEN="your-token"
 npx tsx examples/context/file-search-server/index.ts .
 ```
 
@@ -21,21 +21,7 @@ npx tsx examples/context/file-search-server/index.ts .
 ### Search Files
 ```bash
 curl "http://localhost:3000/search?q=typescript"
-curl "http://localhost:3000/search?q=package.json&format=text"
-```
-
-### Summarize (AI)
-```bash
-curl -X POST http://localhost:3000/summarize \
-  -H "Content-Type: application/json" \
-  -d '{"query":"authentication logic"}'
-```
-
-### Explain Code (AI)
-```bash
-curl -X POST http://localhost:3000/explain \
-  -H "Content-Type: application/json" \
-  -d '{"path":"src/auth.ts"}'
+curl "http://localhost:3000/search?q=authentication+logic"
 ```
 
 ### Health Check

examples/typescript-sdk/context/filesystem-context/index.ts

@@ -11,33 +11,6 @@
  */
 
 import { FileSystemContext } from "@augmentcode/auggie-sdk";
-import { readFile } from "node:fs/promises";
-import { homedir } from "node:os";
-import { join } from "node:path";
-
-/**
- * Read API credentials from ~/.augment/session.json
- * This is a workaround until FileSystemContext supports session file natively
- */
-async function readSessionCredentials(): Promise<{
-  apiKey?: string;
-  apiUrl?: string;
-} | null> {
-  try {
-    const sessionPath = join(homedir(), ".augment", "session.json");
-    const content = await readFile(sessionPath, "utf-8");
-    const data = JSON.parse(content);
-    if (data.accessToken && data.tenantURL) {
-      return {
-        apiKey: data.accessToken,
-        apiUrl: data.tenantURL,
-      };
-    }
-  } catch {
-    // Session file doesn't exist or can't be read
-  }
-  return null;
-}
 
 async function main() {
   console.log("=== FileSystem Context Sample ===\n");
@@ -46,24 +19,10 @@ async function main() {
   const workspaceDir = process.cwd();
   console.log(`Workspace directory: ${workspaceDir}`);
 
-  // Read credentials from session file if not in environment
-  // This allows the example to work after running `auggie login`
-  if (!process.env.AUGMENT_API_TOKEN) {
-    const credentials = await readSessionCredentials();
-    if (credentials) {
-      process.env.AUGMENT_API_TOKEN = credentials.apiKey;
-      process.env.AUGMENT_API_URL = credentials.apiUrl;
-      console.log("✓ Using credentials from ~/.augment/session.json");
-    } else {
-      console.warn(
-        "⚠️  No credentials found. Run 'auggie login' or set AUGMENT_API_TOKEN environment variable."
-      );
-    }
-  } else {
-    console.log("✓ Using credentials from environment variables");
-  }
-
   // Create a FileSystem Context instance
+  // Authentication is handled automatically by the auggie CLI via:
+  // 1. AUGMENT_API_TOKEN / AUGMENT_API_URL env vars, or
+  // 2. ~/.augment/session.json (created by `auggie login`)
   console.log("\nCreating FileSystem Context (spawning auggie --mcp)...");
   const context = await FileSystemContext.create({
     directory: workspaceDir,

examples/typescript-sdk/context/github-action-indexer/README.md

@@ -37,7 +37,7 @@ npm run search "authentication functions"
 npm run search "error handling"
 ```
 
-The index state is saved to `.augment-index-state/state.json` by default, so subsequent runs will perform incremental updates.
+The index state is saved to `.augment-index-state/{branch}/state.json` by default (where `{branch}` is the current branch name), so subsequent runs will perform incremental updates.
 
 ## Deploy to Production (GitHub Actions)
 
@@ -67,12 +67,14 @@ The installation script will:
 
 Add these secrets to your repository (Settings → Secrets and variables → Actions):
 
-| Secret Name | Description | Example |
-|-------------|-------------|---------|
-| `AUGMENT_API_TOKEN` | Your Augment API token | `your-token-here` |
-| `AUGMENT_API_URL` | Your tenant-specific API URL | `https://your-tenant.api.augmentcode.com/` |
+| Secret Name | Description | Required |
+|-------------|-------------|----------|
+| `AUGMENT_API_TOKEN` | Your Augment API token (can be a JSON object with `accessToken` and `tenantURL` fields, or a plain token string) | Yes |
 
-**Note:** `GITHUB_TOKEN`, `GITHUB_REPOSITORY`, and `GITHUB_SHA` are automatically provided by GitHub Actions.
+**Note:**
+- If using a plain token string, you must also set `AUGMENT_API_URL` as a secret or environment variable
+- If your token is a JSON object from `~/.augment/session.json` (with `accessToken` and `tenantURL`), the URL will be extracted automatically
+- `GITHUB_TOKEN`, `GITHUB_REPOSITORY`, and `GITHUB_SHA` are automatically provided by GitHub Actions
 
 ### 3. Push and Run