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

One history. Every agent.

Techlog connects the context scattered across agents, sessions, and engineering tools, so people and AI can understand how problems, decisions, changes, and incidents relate.

An agent records the story as it worksSimulated example

Press Run simulation to watch an agent record the story.

> Merge PR #482 and release 3.8.0 as a canary
● Bash(gh pr merge 482 --squash)
⎿ ✓ Squashed and merged pull request #482 (feat(spin): spin-to-win, 20% cap)
● Bash(gh release create 3.8.0 --prerelease)
⎿ https://github.com/acme/promo-api/releases/tag/3.8.0
● Merged PR #482 and released 3.8.0 as a canary.
> /techlog-record
● /techlog-record(2 events)
⎿ change.implemented time 2026-03-12T09:12:44Z, from the PR merge
⎿ found evt_01J9K2A0P005 Approved spin-to-win: 20% cap
⎿ link implements → evt_01J9K2A0P005 ━━ confirmed
⎿ ✓ recorded evt_01J9K2A0P006
⎿ release.deployed time 2026-03-12T11:02:10Z, from the release
⎿ link releases → evt_01J9K2A0P006 ━━ confirmed
⎿ ✓ recorded evt_01J9K2A0P010
● Recorded both events, each linked to the one it follows from.
── a new session, after 3 days ──
> Investigate PagerDuty alert P1-5521
● Bash(pd incident show P1-5521)
⎿ 5xx ratio 6.2% on /spin triggered 2026-03-15T13:38:00Z
● 5xx started three days after the 3.8.0 canary. That does not prove the release caused it.
> /techlog-record
● /techlog-record(incident.opened)
⎿ time 2026-03-15T13:38:00Z, from the alert
⎿ link observed_after → evt_01J9K2A0P010 ━━ confirmed
⎿ link caused_by → evt_01J9K2A0P006 ┅┅ hypothesis
⎿ ✓ recorded evt_01J9K2A0P011
● Recorded the incident. The suspected cause stays a hypothesis until there is evidence.
> Rollback PR #482
● Bash(kubectl rollout undo deploy/promo-api)
⎿ deployment.apps/promo-api rolled back
● Rolled back the 3.8.0 canary.
> /techlog-record
● /techlog-record(rollback.executed)
⎿ time 2026-03-15T13:51:20Z, from the rollout
⎿ link reverts → evt_01J9K2A0P010 ━━ confirmed
⎿ link mitigates → evt_01J9K2A0P011 ━━ confirmed
⎿ ✓ recorded evt_01J9K2A0P012
● Recorded the rollback. It confirms the mitigation, not the cause.
── a new session, after 1 day ──
> Write the postmortem for P1-5521 and create follow-ups in Jira
● Bash(confluence page create --title "Postmortem 2026-03-16")
⎿ Created page Postmortem 2026-03-16
● Bash(jira issue create --summary "Add 5xx gate to canary promotion")
⎿ OPS-731 Add 5xx gate to canary promotion
● Postmortem written and OPS-731 created.
> /techlog-record
● /techlog-record(2 events)
⎿ postmortem.published time 2026-03-16T10:05:00Z, from the page
⎿ link follows_up → evt_01J9K2A0P011 ━━ confirmed
⎿ ✓ recorded evt_01J9K2A0P013
⎿ action.tracked time 2026-03-16T10:07:30Z, from the ticket
⎿ link follows_up → evt_01J9K2A0P013 ━━ confirmed
⎿ ✓ recorded evt_01J9K2A0P014
● Recorded the postmortem and the corrective action, each linked to what it follows.
── a new session, weeks later ──
> /techlog-record What happened to promo-api in March?
● /techlog-record(history promo-api)
⎿ 3.8.0 canary → 6.2% 5xx → rolled back → postmortem → OPS-731
● The 3.8.0 canary hit 6.2% 5xx and was rolled back. The cause is still a hypothesis: no investigation has confirmed it.

Each /techlog-record call uses the skill to choose the event type, link each event to the ones before it, and mark an unproven cause as a hypothesis.

Open by design. Built for agents.

  • Proposed · draft 0.1

    Open event standard

    A vendor-neutral format for recording and linking engineering events.

    A draft proposal, not a finished standard.

    Explore the standard
  • Implemented · basic

    MCP interface

    Let compatible AI agents record and query engineering history.

    Five tools, such as techlog_record_event, run in the local server.

    Read the MCP guide
  • Local only

    Techlog platform

    A local prototype for storing, connecting, and exploring events.

    There is no hosted service or tool connector yet.

    Run Techlog locally

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