EN
Transparent face derivative of the Kiki cat image supplied by the author
Back to the hall

Kiki

Work signals and agent execution

So that a proposal becomes the assignee's execution.

A Paperclip plugin and a Slack collector that help a team run its AI agents.

2026.04 — 2026.05

pinxlab AI R&D freelance · workflow planning and development, investigating stalled execution and designing the recovery path

  • PluginImplemented · Paperclip
  • MCP serverImplemented · Slack collector

Not how many wake-ups, but whether a run started

The work agent assigned issues is part of what Kiki manages (under development); the assignment and model of the coding agent that fixed it are not recorded.

Full legend

How to read · one grammar for every case

  • Columns are who acted; top to bottom is time
  • Solid: a recorded handoff or next step
  • Heavy lapis ↩: a finding that sent work back
  • Dashed: not a recorded execution (a written rule, advice without authority, an unverified boundary)
  • Rectangle: an action
  • Rounded: an observed state or finding
  • Folded corner: an artifact or evidence
  • Hatched column: parts of the product under development (not the agents used to build it)

April 28, 2026

Context-free wake-ups became an assignment request carrying the issue and the assignee

  1. Under developmentWork agent

    Observation · findingAssigned · lastRunAt empty · only wakeups repeat

    • handoffDid a run start?→ Compare wake-ups: wakeup vs issue + assignee PATCH (Developer)

  2. PersonDeveloper

    ActionCompare wake-ups: wakeup vs issue + assignee PATCH

    • handoffCall with issue context→ After a manual PATCH, one issue stalled 67 hours was queued within 5 seconds (Work agent)

  3. Under developmentWork agent

    Observation · findingAfter a manual PATCH, one issue stalled 67 hours was queued within 5 seconds

    • not a recorded executionScope checked→ Queued ≠ task completed · MTTR not measured (Artifacts)

  4. ArtifactsArtifacts

    Rule · unverifiedQueued ≠ task completed · MTTR not measured

  5. Work sessionRecovery code change

    ActionRecover via assignment PATCH · consecutive no-response cap · cooldown

    • handoff→ Regressions: cap · reset on new activity · legacy path (Artifacts)

  6. ArtifactsArtifacts

    ArtifactRegressions: cap · reset on new activity · legacy path

    • handoff→ Merged · wired into the plugin (Artifacts)

  7. ArtifactsArtifacts

    ArtifactMerged · wired into the plugin

Context
An issue was assigned, yet its run record (lastRunAt) stayed empty while context-free wakeups kept repeating. The key observation was that the assumption “assignment and wake-up activity mean a run” had broken.
Outcome
Recovery became an assignment request carrying the issue and the assignee, and it stops calling again once consecutive no-responses reach the cap. The plugin handler actually receives this assignment request.
Limit
The 67 hours and 5 seconds come from the manual PATCH diagnosis before the change; there is no record of the same timing measured again after the fix was applied. The record goes as far as queue registration; it is not task completion, mean time to recovery or a productivity change. Cross-repository sync in the same work pass needed an admin merge because of a GitHub Actions billing limit, so full CI is not drawn as passing.
Sources and remaining limits
  • The April 29, 2026 doctor check was an install smoke test, not a day-to-day end-to-end run.
  • Deployment, containers and credentials for the plugin bundle belong to an external owner. This does not mean Kiki deployed the whole service.
  • A policy tells implementation sub-agents to name the target branch and to check the returned commit, but no record was found that this procedure applied to this fix.