dsh-agent-lines
For first-time readers

Turn forgetful AI into a team with names, desks, and messages that survive

No architecture, no protocol versions here — just three questions in plain language: what it is, what it guarantees, and what it does not do. Three minutes.

1. What does it feel like?

Picture a small company: every employee has a name and a desk.

  • Name (a "line") = what this role is responsible for. It lasts; changing desks does not change the name.
  • Desk (a "Session") = where the AI currently works. Desks fill up, break, and get replaced — but the name stays.
  • Messages = notes passed between employees. Notes go into a durable tray, so a busy recipient does not lose them.

In one sentence: most AI teams forget everything when the Session ends; this plugin gives each role a long-lived name so the team can keep working.

2. What does it guarantee? (six ground rules)

1. One writer per desk

Only one process writes a Session at a time, so two "people" never scribble on the same record.

2. At least once

A message stays until it is really received; interruptions cause a resend, never a silent drop.

3. Receipt required

The receiver acks after handling. Unacked messages are reported, but never auto-resent — repeating an action can do the work twice.

4. No driving the official wheel

The DSH official Agent Teams plugin (built into DSH) board is read-only for us. Keep using its tasks/panels; we add long-lived role lines alongside.

5. Failures are kept

A failed message is not deleted. You can see where it is stuck and decide to redeliver or purge.

6. No invisible powers

If the runtime lacks a capability, the plugin says so and degrades clearly — it does not pretend or fail silently.

3. Where do I look when something is off?

  • Where is my message? → line_messages by state (queued/delivered/failed).
  • What happened to it? → line_trace: the full lifecycle timeline.
  • Can a failure be rescued? → line_redeliver (human decision, never automatic).
  • Is the team healthy? → doctor: failures, overdue acks, and next steps.

4. What it does not do (up front)

  • No cross-machine, active-active, or strong isolation — it is local-first.
  • No built-in encryption or signing — that is your machine and DSH.
  • No writing back to the official task board — read-only fusion.
  • No per-task exact token billing — only explainable estimates.
  • No full IM — messages are for agent collaboration, not chat.

5. Three sentences to remember

1. A line is a name

The role lasts; the desk can change.

2. Messages survive

At least once; ack means done; redelivery is a human decision.

3. Don't grab the wheel

The official team owns tasks; we own long-lived roles.

Want the full version (seven invariants, five tradeoffs, non-goals) → design philosophy, full.

Get started

Install the plugin · Two ways to use it · GitHub