Skip to content
← Back to the diagram

Saving a correction or repairing a connection

The animation explains the architecture; no live actions are executed.

The diagram describes my maintenance setup.

My correction
  • Preference or clarification

I provide a correction to a preference, context or working rule.

MCP-write
  • Targeted memory update

A specific write function can save the correction outside this chat.

My own context
  • Available for the next question

The saved correction is available for a later question.

Server feedback
  • Reproducible issue

A technical problem is recorded with the original question.

OpenClaw
  • Bounded assignment

OpenClaw passes the report on as a bounded investigation task.

Codex CLI
  • Investigation + patch

Codex can investigate relevant code and prepare a change.

Tests
  • Test the original issue

The change is checked against the reported problem and suitable reference cases.

Repair proposal
  • Review the change

I want to review the change, checks and effects together.

Telegram
  • Approve or reject

Telegram can bring the specific request to me for review.

Apply
  • Only the approved scope

The permitted change is applied within its agreed scope.

Verify
  • Verify and feed back

The original user question is then tried again.

Connections

How to read this

  1. I provide a correction to a preference, context or working rule. A specific write function can save the correction outside this chat. The saved correction is available for a later question.
  2. A technical problem is recorded with the original question.
  3. OpenClaw passes the report on as a bounded investigation task.
  4. Codex can investigate relevant code and prepare a change.
  5. The change is checked against the reported problem and suitable reference cases.
  6. I want to review the change, checks and effects together.
  7. Telegram can bring the specific request to me for review.
  8. The permitted change is applied within its agreed scope.
  9. The original user question is then tried again.
Back to the diagram ↑