[Session] Context injection — pass conversation history to work model #39

New Issue

replit · 2026-03-21T00:35:03Z

replit commented

2026-03-21 00:35:03 +00:00

What

When executing a session work request, prepend the session's prior conversation history to the prompt, and append the completed exchange to history after the response is produced.

Depends on: #38 (session_messages table)

Why

With the table in place but no injection, Timmy still cannot reference prior context. This ticket wires the stored history into the AI call so follow-ups like "now make it shorter" work naturally.

Where to change

artifacts/api-server/src/routes/sessions.ts — POST /sessions/:id/request

Step 1 — Load history before eval (line ~315)

const history = await getSessionHistory(id, 8, 4000);
// history: Array<{ role: "user" | "assistant", content: string }>

Step 2 — Change executeWork call (line ~346)

Add a conversationHistory parameter to AgentService.executeWork (and the streaming variant) so the Anthropic messages array receives all prior turns:

const workResult = await agentService.executeWork(requestText, history);

In agent.ts, build the messages array:

const messages = [
  ...history,                          // prior turns (already role/content objects)
  { role: "user", content: requestText } // current request
];

Pass messages to client.messages.create({ ..., messages }).

Step 3 — Append exchange to history after completion (line ~428, inside the DB transaction)

await tx.insert(sessionMessages).values([
  { sessionId: id, role: "user",      content: requestText,  tokenCount: Math.ceil(requestText.length  / 4) },
  { sessionId: id, role: "assistant", content: result ?? "", tokenCount: Math.ceil((result ?? "").length / 4) },
]);

Only insert on finalState === "complete" — rejected/failed requests are not persisted to history.

Relevant files

artifacts/api-server/src/routes/sessions.ts
artifacts/api-server/src/lib/agent.ts
packages/db/src/index.ts (getSessionHistory helper from #38)

Acceptance

Second request in a session correctly references content from the first
Timmy replies include phrases like "As I mentioned earlier..." when relevant
Rejected requests do not pollute history
Stub mode works unchanged (history injected but model still returns canned response)

## What When executing a session work request, prepend the session's prior conversation history to the prompt, and append the completed exchange to history after the response is produced. **Depends on**: #38 (session_messages table) ## Why With the table in place but no injection, Timmy still cannot reference prior context. This ticket wires the stored history into the AI call so follow-ups like "now make it shorter" work naturally. ## Where to change `artifacts/api-server/src/routes/sessions.ts` — `POST /sessions/:id/request` ### Step 1 — Load history before eval (line ~315) ```typescript const history = await getSessionHistory(id, 8, 4000); // history: Array<{ role: "user" | "assistant", content: string }> ``` ### Step 2 — Change executeWork call (line ~346) Add a `conversationHistory` parameter to `AgentService.executeWork` (and the streaming variant) so the Anthropic `messages` array receives all prior turns: ```typescript const workResult = await agentService.executeWork(requestText, history); ``` In `agent.ts`, build the messages array: ```typescript const messages = [ ...history, // prior turns (already role/content objects) { role: "user", content: requestText } // current request ]; ``` Pass `messages` to `client.messages.create({ ..., messages })`. ### Step 3 — Append exchange to history after completion (line ~428, inside the DB transaction) ```typescript await tx.insert(sessionMessages).values([ { sessionId: id, role: "user", content: requestText, tokenCount: Math.ceil(requestText.length / 4) }, { sessionId: id, role: "assistant", content: result ?? "", tokenCount: Math.ceil((result ?? "").length / 4) }, ]); ``` Only insert on `finalState === "complete"` — rejected/failed requests are not persisted to history. ## Relevant files - `artifacts/api-server/src/routes/sessions.ts` - `artifacts/api-server/src/lib/agent.ts` - `packages/db/src/index.ts` (getSessionHistory helper from #38) ## Acceptance - Second request in a session correctly references content from the first - Timmy replies include phrases like "As I mentioned earlier..." when relevant - Rejected requests do not pollute history - Stub mode works unchanged (history injected but model still returns canned response)

replit added the ai backend labels 2026-03-21 00:35:03 +00:00

replit referenced this issue

2026-03-21 00:35:23 +00:00

[Session] History management — token budget, expiry cleanup, clear endpoint #40

replit referenced this issue

2026-03-21 00:35:46 +00:00

[Session] Frontend — "Clear history" button in session panel #41

claude was assigned by Rockachopa

2026-03-22 23:37:30 +00:00

claude referenced this issue from a commit

2026-03-23 01:51:00 +00:00

feat: inject conversation history into session work model

claude referenced a pull request that will close this issue

2026-03-23 01:51:14 +00:00

[claude] Context injection — pass conversation history to work model (#39) #78

claude closed this issue

2026-03-23 01:51:23 +00:00

claude referenced this issue from a commit

2026-03-23 01:51:24 +00:00

[claude] Context injection — pass conversation history to work model (#39) (#78)

claude commented

2026-03-23 01:51:35 +00:00

PR #78 created.

Changes:

Added session_messages table + migration for storing conversation turns
Added getSessionHistory() helper with turn count and token budget limits
Wired conversation history into executeWork() and executeWorkStreaming() via optional conversationHistory parameter
POST /sessions/:id/request now loads history before the work call and persists user+assistant messages atomically — only on completed requests
Typecheck and lint pass cleanly

PR #78 created. Changes: - Added `session_messages` table + migration for storing conversation turns - Added `getSessionHistory()` helper with turn count and token budget limits - Wired conversation history into `executeWork()` and `executeWorkStreaming()` via optional `conversationHistory` parameter - `POST /sessions/:id/request` now loads history before the work call and persists user+assistant messages atomically — only on completed requests - Typecheck and lint pass cleanly

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: replit/timmy-tower#39