Skip to content

About

Give AI agents a persistent sense of time.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

149 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

TemporalThread

Give AI agents a persistent sense of time.

TemporalThread is a local-first MCP server and CLI that helps AI agents understand when an interaction happened, how much time has passed, what relative phrases meant at the time, and which follow-up commitments are still open.

It stores data locally in SQLite, uses MCP over stdio, opens no network port, collects no telemetry, and does not call an LLM.

It is more than a clock tool. If a user said “Let’s continue tomorrow” at 8:00 PM on July 15 in Bangkok, TemporalThread anchors “tomorrow” to July 16. When the user returns on July 19, it can report that four exact days elapsed and that the commitment is three calendar days overdue—without reinterpreting “tomorrow” using July 19.

Table of Contents

MVP features

  • Nine MCP tools for time, elapsed duration, temporal context, interactions, relative-time resolution, and commitments.
  • Local SQLite persistence across sessions and restarts.
  • Three privacy modes, with temporal-references-only as the default.
  • Deterministic handling of timezones, DST, midnight, leap days, and supported relative expressions.
  • Explicit commitment completion, cancellation, reopening, and rescheduling.
  • CLI commands for setup, diagnostics, timeline, commitments, ingestion, export, verified backup, and purge.
  • Integration guidance for Codex, Claude Code, OpenCode, generic MCP clients, and Ollama examples.

Installation

Install the CLI from npm:

npm install --global temporalthread
temporalthread init

To work from source instead:

Requirements:

  • Node.js 24 or newer
  • pnpm 11.9.0
pnpm install --frozen-lockfile
pnpm build
cd apps/cli
npm link
temporalthread init

Remove a source-linked CLI later with:

npm unlink --global temporalthread

Basic use

Start the local MCP server:

temporalthread start

Initialize a non-interactive generic setup:

temporalthread init --yes --timezone UTC --integration generic --json
temporalthread doctor

Ingest JSON or JSONL events:

temporalthread ingest --file integrations/generic/events.example.jsonl --json
temporalthread timeline

Create a verified SQLite snapshot:

temporalthread backup --output /private/path/temporalthread-backup.sqlite

MCP tools

Tool Purpose
get_current_time Return current UTC and local time context
record_interaction Store an interaction under the selected privacy mode
get_temporal_context Return compact elapsed-time, reference, and commitment context
get_last_interaction Return the latest matching interaction
calculate_elapsed_time Calculate exact duration and calendar-day difference
resolve_relative_time Resolve a phrase against an explicit historical anchor
record_commitment Store an explicit follow-up commitment
list_commitments List pending, due, overdue, completed, or cancelled commitments
update_commitment Complete, cancel, reopen, or reschedule a commitment

All tool inputs and outputs use strict schemas.

Privacy modes

Mode Stored message data
metadata-only Identifiers, timestamps, timezone/offset, and hash
temporal-references-only Metadata plus matched temporal expressions and resolutions; default
full-local-history Metadata, references, preview, and full text

Full history is never enabled automatically.

Host integrations

Codex

temporalthread integrate codex install --scope project --dry-run
temporalthread integrate codex install --scope project --yes
temporalthread integrate codex doctor --scope project

The installer does not approve its own hooks. Review all generated changes and trust prompts.

The Codex package, installer, schemas, hooks, and MCP behavior have repository test coverage. Real Codex CLI/desktop trust, UI, skill discovery, and model behavior remain not tested because live-host certification was skipped.

Claude Code, OpenCode, generic MCP, and Ollama

Setup examples are available under integrations/ and examples/. OpenCode automatic capture remains experimental. Hook-based capture is always best effort and depends on events provided by the host.

See Integrations for the support matrix.

CLI commands

temporalthread init
temporalthread start
temporalthread doctor
temporalthread status
temporalthread config
temporalthread timeline
temporalthread commitments
temporalthread ingest
temporalthread export
temporalthread backup
temporalthread purge
temporalthread integrate codex ...

Use temporalthread <command> --help for command options.

Development

All development is branch-and-PR only. Do not push directly to main.

Normal local checks:

pnpm lint
pnpm typecheck
pnpm test
pnpm build

Run the production dependency audit before dependency or release work:

pnpm audit --prod --audit-level high

Specialized MCP, SQLite recovery, package, artifact, SBOM, and live-host verification scripts are manual tools. They are not required for every commit.

No GitHub Actions workflows are enabled. CI, release automation, tags, releases, publication, and repository visibility changes require explicit owner approval.

Current release status

TemporalThread v0.1.0 was published to npm and GitHub on July 29, 2026. It is an MVP release, not a claim of production readiness.

The CLI, package, installer, privacy boundaries, and MCP behavior have automated local coverage. Real Codex CLI/desktop trust, UI, skill discovery, lifecycle delivery, and model behavior remain uncertified, and hook-based capture remains best effort.

See the live Codex certification results for the untested host surfaces.

Documentation

TemporalThread is available under the MIT License.


About

I'm Sudarshan Chaudhari, a Senior Quality Engineer, Test Automation specialist, and AI systems builder based in Bangkok, Thailand.

I have 13+ years of experience in software quality engineering, working across SaaS, fintech, gaming, web, mobile, cloud, and digital signage platforms. My background combines hands-on test automation with QA leadership, test strategy, CI/CD, release quality, production investigation, and cross-platform validation.

Alongside my professional QA career, I run SudarshanTechLabs, my independent engineering and product lab where I design, build, test, and ship software across Android, web, AI, cybersecurity, developer tooling, and cross-platform applications.

What I work on

  • ⚙️ Quality Engineering & Test Automation — Playwright, Selenium, Cypress, Appium, API testing, automation frameworks, end-to-end testing, CI/CD, release gates, GitHub Actions, risk-based testing, and production validation
  • 🤖 AI Systems & Automation — AI agents, multi-agent orchestration, MCP servers, AI-assisted QA, prompt tooling, developer workflows, automation systems, and Claude Code plugins
  • 📱 Mobile & Cross-Platform Applications — Android applications built with Kotlin and Jetpack Compose, Google Play releases, automated build and publishing pipelines, and cross-platform development spanning iOS, web, Windows, and macOS
  • 🌐 Web Applications & Platforms — Full-stack applications using Next.js, TypeScript, Firebase, Cloudflare, REST APIs, and modern web infrastructure
  • 🛠️ Developer Tooling & CLI Engineering — Rust, Python, TypeScript, CLI utilities, multi-repository tooling, build automation, release tooling, and engineering productivity systems
  • 🛡️ Cybersecurity & Observability — Threat detection, log analysis, security auditing, vulnerability assessment, monitoring, and security-focused developer tools
  • 📺 Digital Signage & Device Platforms — Content validation, playback testing, device compatibility, production investigation, monitoring, and QA across diverse hardware and operating-system environments

My work sits at the intersection of quality engineering, automation, AI, and software development. I approach products with a QA mindset from the beginning: understanding failure modes, designing for testability, automating repetitive work, and building release confidence into the engineering process.

Through SudarshanTechLabs, I also build products and tools from idea to production, covering architecture, development, testing, CI/CD, release automation, monitoring, and ongoing maintenance.

🌐 sudarshantechlabs.com · 💼 LinkedIn · 🐙 GitHub · ✉️ sunny.sudarshan@gmail.com

About

Give AI agents a persistent sense of time.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages