Skip to content

feat: add temporal context engine#379

Merged
xlabtg merged 4 commits intoxlabtg:mainfrom
konard:issue-378-981903a53dde
Apr 24, 2026
Merged

feat: add temporal context engine#379
xlabtg merged 4 commits intoxlabtg:mainfrom
konard:issue-378-981903a53dde

Conversation

@konard
Copy link
Copy Markdown

@konard konard commented Apr 24, 2026

Fixes #378

Summary

  • Adds temporal context configuration, timezone override via TELETON_TIMEZONE, temporal metadata storage, and time pattern tables with schema migration 1.31.0 after the latest upstream migrations.
  • Adds TemporalContextService for metadata indexing, behavior pattern analysis, active temporal context snapshots, timeline retrieval, and temporal relevance weighting in memory search.
  • Wires temporal context into runtime prompts, knowledge/message/behavior indexing, WebUI memory search, and new /api/context endpoints.
  • Preserves upstream pipeline execution and self-correction changes while resolving merge conflicts with main.
  • Adds an Analytics Temporal Context panel for current time context, active patterns, learned pattern toggles, and timeline entries.
  • Bumps teleton to 0.8.12 for the next release.

Verification

  • npm ci
  • npm run build:sdk
  • npm test -- src/memory/tests/schema.test.ts src/services/tests/temporal-context.test.ts
  • npm run typecheck
  • Earlier full branch verification before the upstream merge: npm run lint, npm test, npm run build, npm run audit:ci, and Playwright/Chrome screenshot checks for desktop and mobile Analytics Temporal Context render.

Screenshot

Temporal Context Analytics

Adding .gitkeep for PR creation (default mode).
This file will be removed when the task is complete.

Issue: xlabtg#378
@konard konard changed the title [WIP] v2-11-temporal-context feat: add temporal context engine Apr 24, 2026
@konard konard marked this pull request as ready for review April 24, 2026 02:57
@konard
Copy link
Copy Markdown
Author

konard commented Apr 24, 2026

Solution summary

Implemented and pushed the Temporal Context Engine work.

PR 379 is ready for review: #379
Commit: 3e745d5 feat: add temporal context engine

Verification passed:

  • npm run typecheck
  • npm run lint
  • npm test - 3293 tests passed
  • npm run build
  • npm run audit:ci
  • Upstream GitHub Actions are green for latest SHA 3e745d5

Screenshot included in the PR:
https://github.com/konard/xlabtg-teleton-agent/blob/issue-378-981903a53dde/docs/screenshots/temporal-context-analytics.png?raw=true

Working tree is clean.


This summary was automatically extracted from the AI working session output.

@konard
Copy link
Copy Markdown
Author

konard commented Apr 24, 2026

🤖 Solution Draft Log

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

  • Model: GPT-5.5
  • Provider: OpenAI
  • Public pricing estimate: $27.635679

📊 Context and tokens usage:

  • 42.2M / 1.1M (4023%) input tokens, 91.0K / 130K (70%) output tokens

Total: (841.3K + 41.4M cached) input tokens, 91.0K output tokens, $27.635679 cost

🤖 Models used:

  • Tool: OpenAI Codex
  • Requested: gpt-5.5
  • Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (2 chunks) (144839KB)


Now working session is ended, feel free to review and add any feedback on the solution draft.

@konard
Copy link
Copy Markdown
Author

konard commented Apr 24, 2026

✅ Ready to merge

This pull request is now ready to be merged:

  • All CI checks have passed
  • No merge conflicts
  • No pending changes

Monitored by hive-mind with --auto-restart-until-mergeable flag

@konard konard marked this pull request as draft April 24, 2026 03:15
@konard
Copy link
Copy Markdown
Author

konard commented Apr 24, 2026

🤖 AI Work Session Started

Starting automated work session at 2026-04-24T03:15:42.638Z

The PR has been converted to draft mode while work is in progress.

This comment marks the beginning of an AI work session. Please wait for the session to finish, and provide your feedback.

@konard konard marked this pull request as ready for review April 24, 2026 03:23
@konard
Copy link
Copy Markdown
Author

konard commented Apr 24, 2026

Solution summary

Resolved the upstream merge conflicts and pushed the branch.

PR 379 is now ready for review: #379

What changed:

  • Merged latest upstream/main into issue-378-981903a53dde.
  • Kept upstream pipeline execution and self-correction work.
  • Kept this branch’s temporal context engine.
  • Moved the temporal DB migration to schema 1.31.0 so it follows upstream 1.29.0 pipeline and 1.30.0 correction migrations.
  • Updated the PR description accordingly.

Verification passed locally:

  • npm ci
  • npm run build:sdk
  • npm test -- src/memory/__tests__/schema.test.ts src/services/__tests__/temporal-context.test.ts
  • npm run typecheck

Current PR state:

  • Mergeable: yes
  • Draft: no
  • CI: running on latest SHA 6a5389a; some checks already succeeded, others still in progress at the time of my last check.
  • Working tree: clean.

This summary was automatically extracted from the AI working session output.

@konard
Copy link
Copy Markdown
Author

konard commented Apr 24, 2026

🤖 Solution Draft Log

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

  • Model: GPT-5.5
  • Provider: OpenAI
  • Public pricing estimate: $4.480694

📊 Context and tokens usage:

  • 6.8M / 1.1M (650%) input tokens, 13.5K / 130K (10%) output tokens

Total: (147.3K + 6.7M cached) input tokens, 13.5K output tokens, $4.480694 cost

🤖 Models used:

  • Tool: OpenAI Codex
  • Requested: gpt-5.5
  • Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Gist (22682KB)


Now working session is ended, feel free to review and add any feedback on the solution draft.

@xlabtg xlabtg merged commit e32d589 into xlabtg:main Apr 24, 2026
18 checks passed
@xlabtg xlabtg mentioned this pull request Apr 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

v2-11-temporal-context

2 participants