TypeScript SDK Examples

[igor0]

Add comprehensive TypeScript SDK context examples demonstrating core functionality

This PR introduces four practical examples showcasing different use cases of the Auggie TypeScript SDK's context capabilities:

• Direct Context (direct-context/index.ts) - Demonstrates basic usage patterns including simple file indexing, persistent index management across sessions, batch upload optimization, and external LLM integration
• File Search Server (file-search-server/index.ts) - Implements a REST API server providing semantic file search with AI-powered summarization, including /search and /ask endpoints
• FileSystem Context (filesystem-context/index.ts) - Shows automatic file discovery and indexing from local directories using the MCP protocol
• Prompt Enhancer Server (prompt-enhancer-server/index.ts) - Provides an HTTP server that automatically enriches user prompts with relevant codebase context via /enhance and /enhance-and-ask endpoints

These examples provide developers with ready-to-use patterns for integrating semantic code search, context-aware AI interactions, and codebase indexing into their applications.

---

🤖 This description was generated automatically. Please react with 👍 if it's helpful or 👎 if it needs improvement.

[github-actions]

I've reviewed the TypeScript SDK examples. The code demonstrates the SDK functionality well with clear examples. I found one potential security concern regarding path validation in the server examples.

---

🤖 Automated review complete. Please react with 👍 or 👎 on the individual review comments to provide feedback on their usefulness.

[github-actions]

The directory parameter from command-line arguments is passed directly to initializeContext without validation. This could allow an attacker to read arbitrary directories on the system if they can control the command-line arguments.

Consider adding path validation to ensure the directory is within expected bounds:

import { resolve } from 'path';

async function main() {
  const directory = process.argv[2] || process.cwd();
  const resolvedDir = resolve(directory);
  
  // Validate the directory exists and is accessible
  try {
    const stat = statSync(resolvedDir);
    if (!stat.isDirectory()) {
      throw new Error('Path is not a directory');
    }
  } catch (error) {
    console.error('Invalid directory:', error);
    process.exit(1);
  }
  
  console.log('Starting File Search Server...');
  await initializeContext(resolvedDir);
  // ...
}

[github-actions]

The directory parameter from command-line arguments is passed directly to initializeContext without validation. This could allow an attacker to read arbitrary directories on the system if they can control the command-line arguments.

Consider adding path validation to ensure the directory is within expected bounds:

import { resolve } from 'path';

async function main() {
  const directory = process.argv[2] || process.cwd();
  const resolvedDir = resolve(directory);
  
  // Validate the directory exists and is accessible
  try {
    const stat = statSync(resolvedDir);
    if (!stat.isDirectory()) {
      throw new Error('Path is not a directory');
    }
  } catch (error) {
    console.error('Invalid directory:', error);
    process.exit(1);
  }
  
  console.log('Starting Prompt Enhancer Server...');
  await initializeContext(resolvedDir);
  // ...
}

[igor0]

augment review

[richhankins]

LGTM!