Techlog

Connect Engineering Work

Every problem, decision, code change, release, and incident becomes part of a connected engineering history that AI agents can record, search, and build on.

Legacy Changelog

  • 1 · Problem💬 Slack“Why a 20% cap?”
  • 2 · Decision🎫 JiraSPIN-214 · cap approved
  • 3 · Change🔀 GitHubPR #482 · spin-to-win
  • 4 · Release🚀 GitHubRelease 3.8.0 · canary
  • 5 · Incident🚨 PagerDutyP1 · 5xx at 6.2%
  • 6 · Rollback💬 Slack“Rolling back, I think?”
  • 7 · Postmortem📄 ConfluencePostmortem 2026-03-12
  • 8 · Corrective action🎫 JiraOPS-731 · 6 actions
  • 🤖 AI agentClaudeOpens PR #482
  • 🤖 AI agentCodexWrites the postmortem
Read the docs

How it works

Capture. Connect. Use.

Techlog connects engineering context across agents, sessions, and the tools you already use. It is not another place to store artifacts, and it does not replace GitHub, Jira, Slack, your docs, code review, or engineering judgment.

  1. 1

    Agents capture context

    AI agents record engineering problems, decisions, code changes, releases, and incidents as work evolves.

    Capture the why, not just the code.

  2. 2

    Techlog connects events

    Related events are linked across tools. Provenance and evidence are kept, and a confirmed link is told apart from a hypothesis.

    One connected engineering history.

  3. 3

    Agents find answers

    AI agents query past decisions, investigate incidents, find similar failures, and reuse earlier investigations.

    Turn engineering history into useful context.

One story across tools
  1. Code changeGitHub · PR #482
  2. ReleaseGitHub · 3.8.0
  3. IncidentPagerDuty · P1hypothesis
  4. RollbackSlack · threadconfirmed
  5. PostmortemConfluence
  6. Corrective actionJira · OPS-731

A solid link is confirmed by evidence. A dashed link is a hypothesis, such as a release suspected of causing an incident, until evidence confirms it. Agents or people can add more links later.

  • Proposed · draft 0.1

    Open event standard

    What an event looks like, so any tool can write and read it.

  • Implemented · basic

    MCP interface

    How agents record and query events, such as techlog_record_event.

  • Local only

    Techlog platform

    Stores and links events. A basic server runs locally; there is no hosted service or tool connector yet.

Run it on your machine today.

A basic Techlog server runs locally with the example story loaded. Or read how the event model works first.

Read the docs