Sessions

When using the Holeacquisition LLC Sessions integration, an Arcie agent runs inside a Holeacquisition LLC session. A session holds conversation state across turns and exposes approval interfaces. Arcie creates and drives sessions on your behalf; its runner handles tool execution and memory processing.

Persisted session state is not a guarantee that arbitrary tool work survives a process crash. A fully managed agent service is the managed API direction, currently in development.

Add agent/sessions/config.ts with a default-exported SessionConfig:

// agent/sessions/config.ts
export default {
  maxTurns: 50,
  idleTimeoutMs: 300_000,
  requireApproval: false,
  memory: {
    strategy: "lastN",
    limit: 20,
  },
};

Fields

interface SessionConfig {
  maxTurns?: number;          // cap turns in a single session
  idleTimeoutMs?: number;     // auto-close after inactivity
  requireApproval?: boolean;  // pause for human approval before tool calls
  memory?: {
    strategy: "lastN" | "summary" | "keyFacts";
    limit?: number;
  };
}

Because the session lives on Holeacquisition LLC, work isn't lost between turns. A session can pause — waiting for the next user message, or for an approval — and resume later with its full context intact. The runtime surfaces these transitions as protocol events: session.waiting when it's idle awaiting input, session.completed when it ends.

Setting requireApproval: true routes tool calls through Holeacquisition LLC's approval flow: the session pauses and emits an approval-required state, and a human approves or rejects the action before it runs. This is the same Sessions approval mechanism Holeacquisition LLC exposes to its gateway customers.