aside-google-gmail

Gmail

Use the gmail global in the REPL tool. It uses direct HTTP against Gmail's internal sync API — no tab navigation needed.

IMPORTANT: User may use multiple Google accounts (e.g. work email / personal email). ALWAYS CALL await googleAccounts.print() to print all logged-in google accounts and identify the correct uid before using Gmail.

• Every gmail method takes uid (the /u/{uid}/ index) as its first argument.
  • Use browser history search and memory search to get hint about the account to use.
• If intended search results are empty, consider trying a different uid. Use Promise.all for searching multiple accounts.
• NOTE THAT threadId is different between accounts even if it refers to the same thread.

Quick Reference

const uid = 1; // uid from Google Accounts list

// Inbox and Search
const inbox = await gmail.getInbox(uid); // shorthand for search(uid, 'in:inbox')
const searchResults = await gmail.search(uid, 'from:[email protected] subject:"meeting"');
// → { results: GmailSearchResult[], hasMore, total, nextOffset }

// Read thread (body is markdown by default)
const thread1 = await gmail.getThread(uid, 'thread-f:123456');
// → { threadId, subject, messages: GmailThreadMessage[] }

// Compose (opens tab with pre-filled fields, returns Playwright Page)
const cp1 = await gmail.openComposer(uid, { to: '[email protected]', subject: 'Hi', bodyHtml: '<b>Hello</b>' });

// Reply (opens inline reply in thread detail page, returns Playwright Page)
const rp1 = await gmail.openReplyComposer(uid, { threadId: 'thread-f:123456', bodyHtml: '<p>Thanks</p>' });

// Download attachment
await gmail.downloadAttachment(uid, attachment.url, 'report.pdf');

Methods

gmail.search(uid: number, query: string, opts?: { offset?: number }): Promise<GmailSearchResponse>

Search threads via Gmail search operators (from:, to:, subject:, label:, before:, after:, is:, has:attachment, etc.).

• uid — Google account index (/u/{uid}/).
• query — Gmail search query string.
• opts.offset — Pagination offset (default 0). Use nextOffset from previous response.