Instructions for AI coding agents working on this Val Town project.

Meeting recording automation platform for Val Town:

• Send bots to meetings via Recall.ai
• Manage recordings with transcripts
• Val Town SQLite database
• Single-file deployment in val.ts

1. All code goes in val.ts - Single file deployment
2. Use esm.sh imports: import { Hono } from "https://esm.sh/hono@4"
3. Val Town SQLite: import { sqlite } from "https://esm.town/v/std/sqlite"
4. Parameterized queries: Always use ? placeholders
5. TypeScript: Explicit types for all functions

const result = await db.execute({
  sql: `SELECT * FROM table WHERE id = ?`,
  args: [id],
});

const row = firstRow<TypeName>(result);

const id = crypto.randomUUID();
const now = Date.now();

await db.execute({
  sql: `INSERT INTO table (id, field, created_at) VALUES (?, ?, ?)`,
  args: [id, value, now],
});

API endpoints are split between two patterns matching Django structure:

API Pattern (under /api/ prefix):

app.get("/api/recordings", authMiddleware, async (c) => {
  const user = c.get("user");
  const db = getDb();

  const result = await db.execute({
    sql: `SELECT * FROM recordings WHERE user_id = ?`,
    args: [user.id],
  });

  return c.json({ recordings: parseRows(result) });
});

Action Pattern (root level):

app.post("/recordings/upload", authMiddleware, async (c) => {
  const user = c.get("user");
  const body = await c.req.json();
  // Handle upload logic
  return c.json({ success: true });
});

• API endpoints (/api/*): Read operations, list views
• Action endpoints (root level): Create, update, action operations
• Webhooks (/webhooks/*): External webhook handlers (no auth)

Tables:

• users - User accounts (id, email, api_token, etc.)
• recordings - Meeting recordings (id, user_id, recallai_bot_id, title, etc.)
• clips - Video clips (id, recording_id, title, video)
• calendar_events - Calendar events (id, user_id, raw, start_time, end_time)
• calendar_preferences - User automation rules (id, user_id, enabled, ruleset)
• calendar_series_preferences - Recurring meeting preferences

Field types:

• IDs: TEXT (UUIDs)
• Timestamps: INTEGER (milliseconds)
• Booleans: INTEGER (0/1)
• JSON: TEXT (stringify/parse)

Access via Deno.env.get("VAR_NAME"):

• RECALLAI_API_KEY - Required
• AWS_ACCESS_KEY_ID - Required
• AWS_SECRET_ACCESS_KEY - Required
• AWS_STORAGE_BUCKET_NAME - Required
• JWT_SECRET - Required

• ❌ Split code into multiple files
• ❌ Use JSR imports (jsr:@hono/hono)
• ❌ Use local file system
• ❌ Add voice print/ML features
• ❌ Hardcode secrets
• ❌ Use SQL string concatenation

• ✅ Keep everything in val.ts
• ✅ Use esm.sh for imports
• ✅ Use Val Town SQLite
• ✅ Use parameterized queries
• ✅ Handle errors gracefully
• ✅ Log important operations
• ✅ Return proper HTTP status codes

1. Copy val.ts to Val Town
2. Set environment variables in Val Town UI
3. Create first user via script Val
4. Test endpoints

# Health check
curl https://yourval.web.val.run/health

# List recordings
curl -H "Authorization: Token YOUR_TOKEN" \
  https://yourval.web.val.run/api/recordings

# Send bot
curl -X POST https://yourval.web.val.run/recordings/send_bot \
  -H "Authorization: Token YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"meeting_url": "https://zoom.us/j/123", "title": "Test"}'

• Val Town: https://val.town
• Val Town Docs: https://docs.val.town
• Hono.js: https://hono.dev
• Recall.ai: https://docs.recall.ai