Time Strike

Time Strike

Time Strike is a small, native Rust [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server that turns a human deadline into compact, deterministic control signals for an autonomous agent. It helps an agent decide how much work to start, when to validate, when to converge, and when to stop.

Time Strike is deliberately local-first: it does not run an LLM, make network requests, inspect repositories, execute shell commands, schedule calendar events, or send messages. It exposes five MCP tools over stdio and keeps the policy engine independent from MCP so it can be tested and embedded predictably.

Features

• Monotonic runtime accounting using std::time::Instant.
• Deterministic O(1) tick policy decisions.
• Adaptive validation and finalization reserves.
• Automatic modes: explore, execute, converge, validate, finalize, emergency, and expired.
• Automatic schedule pressure: ahead, on_track, behind, and critical.
• Action caps, next-check intervals, and must_* control flags.
• Parent/child budget clamping with thread-safe task state.
• Optional atomic JSON persistence; downtime is charged during recovery.
• Compatible with Claude Desktop, Claude Code, Codex, Hermes Agent, and generic MCP stdio clients.

See it in action: a five-minute chat task

Imagine asking an AI coding agent for a useful result under a hard deadline:

**You:** Review this pull request and give me the three highest-risk findings. You have five minutes.

**Agent:** I’ll time-box the review and reserve time to validate the findings.

`Time Strike · start_task(budget_seconds: 300)`

**Agent:** I inspected the changed authentication and database paths. Time Strike says I’m on schedule, with 168 seconds available for new work.

`Time Strike · tick() → mode: converge, must_converge: true`

**Agent:** I’ll stop exploring unrelated files, confirm the three strongest findings, and prepare the answer.

`Time Strike · tick()