Gemini Interactions API previous_interaction_id Example

Example data model

For a small app, store interaction state separately from user-facing messages:

type GeminiJob = {
  id: string;
  userId: string;
  task: string;
  firstInteractionId: string | null;
  latestInteractionId: string | null;
  environmentId: string | null;
  status: "queued" | "running" | "done" | "failed";
  createdAt: string;
  updatedAt: string;
};

First request and follow-up request

const first = await ai.interactions.create({
  model: "gemini-3.5-flash",
  input: "Draft a migration plan from REST endpoints to typed SDK calls.",
});

await saveJobState({
  firstInteractionId: first.id,
  latestInteractionId: first.id,
});

const second = await ai.interactions.create({
  model: "gemini-3.5-flash",
  previous_interaction_id: first.id,
  input: "Turn that migration plan into a 10-step checklist.",
});

For Antigravity Agent work, keep the same pattern but include the agent and environment fields supported by the current docs.

Debugging state loss

If a follow-up call behaves like a fresh request, check these in order:

1. The ID came from the previous API response.
2. The previous interaction was created with the same account and project.
3. The request used the correct field name and API revision.
4. The interaction or environment has not expired.
5. Your application did not overwrite latestInteractionId with a local job ID.