Agent Reflection: Summarize Sessions with Local Agents

[alexchaomander]

This PR adds the 'cloudcode summary ' command. It allows users to pipe their clean semantic transcripts into their local AI agents (Claude, Gemini, etc.) to generate concise session summaries or PR descriptions. Includes 0600 privacy hardening for temporary context files.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[gemini-code-assist]

Code Review

This pull request introduces the cloudcode summary command, which enables users to generate architectural and session summaries using local AI agents. The implementation involves fetching session transcripts, creating temporary prompt files, and managing agent execution within tmux sessions. Feedback highlights several areas for improvement: replacing brittle fixed-duration timeouts with polling for agent readiness, resolving a race condition in temporary file cleanup by using synchronous file operations, improving type safety by defining interfaces instead of using any, and refactoring the large command handler into smaller, more manageable functions.

[gemini-code-assist]

Using a fixed-duration setTimeout to wait for the agent to boot is brittle. The agent might take longer to start under certain conditions, leading to race conditions where the next command is sent too early. A more robust approach is to poll the tmux pane until a prompt or some initial output appears, indicating the agent is ready. This ensures the script waits for as long as necessary, but no longer.

[gemini-code-assist]

The temporary file cleanup is unreliable. The exit event handler is synchronous, but import('fs').then(...) is asynchronous. This creates a race condition where the process may exit before the file is deleted.

To ensure cleanup happens, you should use the synchronous unlinkSync function.

First, add unlinkSync to your import statement at the top of the file (line 12):

import { writeFileSync, chmodSync, unlinkSync } from 'fs';

Then, replace this block with a simple synchronous call:

Suggested change

	try {
	// fs.unlinkSync(tmpPromptPath);
	// Leaving it might be useful if they want to see what was sent, but better to clean up.
	import('fs').then(fs => fs.unlinkSync(tmpPromptPath)).catch(() => {});
	} catch {}
	try {
	const fs = require('fs');
	fs.unlinkSync(tmpPromptPath);
	} catch {
	// Best-effort cleanup, ignore errors.
	}

[gemini-code-assist]

This action handler is over 100 lines long and handles multiple distinct steps (fetching data, creating files, running tmux, etc.). For better readability, maintainability, and testability, consider refactoring it into smaller, single-purpose helper functions.

For example, you could have functions like:

• getSessionAndProfile(id, agentSlug)
• createSummaryPromptFile(transcript)
• launchSummaryAgent(profile, promptPath, workdir)

[gemini-code-assist]

Using as any bypasses TypeScript's type safety. It's better to define a type for the data you expect from the database to catch potential errors and improve code clarity.

For example:

type AgentProfileFromDb = {
  name: string;
  command: string;
  args_json: string;
  env_json: string;
  // ... other fields you use
};

const profile = db.prepare('SELECT * FROM agent_profiles WHERE slug = ?').get(options.agent) as AgentProfileFromDb | undefined;

[gemini-code-assist]

Using Date.now() for temporary filenames can lead to collisions if the command is executed multiple times within the same millisecond. Since nanoid is already a dependency, using it would generate a more robust and unique filename.

Suggested change

	const tmpPromptPath = join(tmpdir(), `cc-summary-${id}-${Date.now()}.md`);
	const tmpPromptPath = join(tmpdir(), `cc-summary-${id}-${nanoid(8)}.md`);