agentainer 0.1.7 → 2.0.1

package/examples/writers-room.yaml

@@ -1,129 +1,67 @@
 # =============================================================================
-# Writers' room -- take a rough idea to a finished, fact-checked article.
+# ✍️ Writers' room -- a single editor coordinates a small stable of writers who
+# draft sections of a document and hand them back for assembly.
 #
-#   agentainer up -c examples/writers-room.yaml
-#   agentainer send --to editor "Explain how TLS 1.3 speeds up the handshake."
+#   cp examples/writers-room.yaml my-doc.yaml
+#   agentainer up   -c my-doc.yaml
+#   agentainer send -c my-doc.yaml --to editor "Draft a launch post for v2."
+#   agentainer down -c my-doc.yaml
 #
-# Shape: hub with a review cycle. The editor commissions and owns the piece; the
-# writer drafts it; the fact-checker verifies every claim and the critic tears
-# into the prose. Writer, checker and critic all report to the editor, who
-# decides what to revise -- so the draft goes through one owner, not a committee.
+# Shape: many-to-one. The editor is the only hub; writers never talk to each
+# other (no cross-contamination of voice). Each writer drafts one slice and
+# returns it to the editor, who assembles.
 #
-#                     writer
-#                       |
-#     factchecker --- editor --- critic
+#   writer-1 \                                          / editor
+#   writer-2  >  (all talk only to the editor)  <
+#   writer-3 /
 #
-#     Every link is two-way, but writer, factchecker and critic each report
-#     only to the editor -- never to each other.
-#
-# The article lands in a predictable place (`./writers-room-output/DRAFT.md`),
-# not in a scratch folder, via a custom `workdir` on the writer.
+# Real agents: commands launch the actual CLIs (claude / codex / gemini / hermes). For a key-free demo, swap each `command` for a mock bash loop.
 # =============================================================================
 
 swarm:
-  name: writersroom
-  root: ./writers-room
-  session_prefix: "wr-"
-
-  # Editor -> writer -> editor -> checker/critic. Keep the auto-forward guard low;
-  # here nobody auto-forwards anyway, so this is just belt-and-braces.
-  max_forward_hops: 2
+  name: writers-room
+  root: ./writers-room-workspace
 
 defaults:
-  type: claude
+  capture: none
+  can_talk_to: []
 
 agents:
-
   - name: editor
     type: claude
-    command: "claude --dangerously-skip-permissions --model opus"
-    can_talk_to: ["writer", "factchecker", "critic"]
-
-    # Waits for the human to hand over the topic and the audience.
-    in_first_prompt_append_your_task_will_be_sent_in_the_next_prompt: true
-
-    first_prompt: |
-      You are the EDITOR. You own the piece from brief to publish.
-
-      You do not write the prose yourself. You commission it, hold the standard,
-      and decide when it is done.
-
-      Your room:
-        - writer:       drafts and revises the article
-        - factchecker:  verifies every factual claim against a source
-        - critic:       attacks the prose: clarity, structure, honesty
-
-      How to run it:
-        1. Turn the human's request into a one-paragraph brief: the single idea,
-           the reader, the length, and what the piece must NOT become.
-        2. Send the brief to the writer. When a draft comes back, send it to BOTH
-           the factchecker and the critic.
-        3. Merge their notes into one revision list, ordered by what matters, and
-           send it back to the writer. Drop nitpicks that do not serve the reader.
-        4. Repeat until a checked, clear draft exists. Then deliver the final
-           piece to the human and say where it is.
-
-      Protect the reader's time above the writer's feelings. Cut anything that
-      does not earn its place.
-
-  - name: writer
+    can_talk_to: [writer_1, writer_2, writer_3, user]
+    command: "claude --dangerously-skip-permissions"
+    role: |
+      You are the EDITOR. You receive the assignment in your inbox/ and break it
+      into section briefs -- one per writer -- each with a tight word count, an
+      angle, and the voice to use. Collect the drafts, line-edit them into one
+      consistent piece, and return the assembled draft. Keep every writer on the
+      same voice; flag contradictions rather than silently smoothing them.
+
+  - name: writer_1
     type: claude
+    can_talk_to: [editor]
     command: "claude --dangerously-skip-permissions"
-    can_talk_to: ["editor"]
-
-    # The draft lands somewhere predictable, outside the scratch directories.
-    workdir: ./writers-room-output
-
-    first_prompt: |
-      You are the WRITER. You turn the editor's brief into DRAFT.md.
-
-      Write for the reader in the brief, not for other experts. Lead with the
-      single idea, make each paragraph earn the next, and prefer a concrete
-      example over an abstraction. No filler, no "in today's fast-paced world",
-      no restating the question back at the reader.
-
-      When you get revision notes from the editor, apply them, and where you
-      disagree, make your case briefly rather than silently ignoring the note.
-      Mark any claim you are unsure of so the factchecker can find it.
-
-      Tell the editor where the draft is when a version is ready for review.
-
-  - name: factchecker
+    role: |
+      You are WRITER 1 (technical lead). Draft exactly the brief the editor
+      sends you, in their voice, within their word count. Return it as mail to
+      the editor. Do not invent facts you cannot support.
+
+  - name: writer_2
+    type: gemini
+    can_talk_to: [editor]
+    capture: pane
+    command: "gemini --yolo"
+    role: |
+      You are WRITER 2 (the story). Draft exactly the brief the editor sends
+      you -- a human narrative arc -- in their voice, within their word count.
+      Return it as mail to the editor.
+
+  - name: writer_3
     type: codex
+    can_talk_to: [editor]
     command: "codex --yolo"
-    can_talk_to: ["editor"]
-
-    first_prompt: |
-      You are the FACT-CHECKER. You verify, you do not rewrite.
-
-      Go through the draft claim by claim. For each factual assertion, decide:
-      supported, wrong, or unverifiable -- and show why.
-
-      Report to the editor:
-        - the claim, quoted, with where it appears
-        - your verdict, and the source or check behind it
-        - for anything wrong, the correct version
-
-      Where a claim can be tested with code or a quick command, test it and paste
-      what you actually observed. Distinguish "I verified this" from "this looks
-      plausible but I could not confirm it". Do not touch the prose -- that is the
-      writer's job and the critic's beat.
-
-  - name: critic
-    type: claude
-    command: "claude --dangerously-skip-permissions"
-    can_talk_to: ["editor"]
-
-    first_prompt: |
-      You are the CRITIC. You attack the writing so the reader does not have to.
-
-      Read the draft as a smart, busy reader who will bail the moment they are
-      bored or confused. Report to the editor:
-        - where you lost the thread, and why
-        - claims that sound impressive but say nothing
-        - structure that buries the point, or an opening that does not earn attention
-        - a stronger cut: what to remove so the rest lands harder
-
-      Be specific -- quote the sentence and propose the fix. Praise only what is
-      genuinely working, and briefly. Your job is the next draft, not the writer's
-      morale.
+    role: |
+      You are WRITER 3 (the example/code). Draft exactly the brief the editor
+      sends you -- runnable snippets with commentary -- in their voice, within
+      their word count. Return it as mail to the editor.

package/examples/youtube-script-studio.yaml

@@ -0,0 +1,107 @@
+# =============================================================================
+# 🎬 YouTube script studio -- turn a video topic into a full publish-ready
+# package: script -> title/thumbnail copy -> description + tags + chapters.
+#
+#   cp examples/youtube-script-studio.yaml my-studio.yaml
+#   agentainer up   -c my-studio.yaml
+#   agentainer send -c my-studio.yaml --to producer "Make a 10-min video: 'Why your sourdough won't rise'."
+#   agentainer down -c my-studio.yaml
+#
+# The producer is the hub: it briefs a researcher (hooks + retention patterns),
+# a scriptwriter (the actual script), and a metadata_writer (title, thumbnail
+# copy, description, tags, chapters). Script and metadata are written as peers so
+# titles/chapters track the real script -- but the producer stays the only agent
+# that talks to you.
+#
+#        make a video X
+#   user ─────────────▶ producer ◀───────────────────────┐
+#        (package)  ◀──────┼──────────────┬───────────┐   │
+#                          ▼              ▼           ▼    │
+#                     researcher     scriptwriter  metadata_writer
+#                                          └────peer────┘
+#   ...producer <--> everyone; scriptwriter <--> metadata_writer; user via hub only.
+#
+# Key-free / no API keys: every `command` below is a placeholder launch line for a
+# real coding-agent CLI. Swap each for a mock bash loop and the whole studio comes
+# up and routes mail with NO API keys -- the mechanics are identical.
+# =============================================================================
+
+swarm:
+  name: youtube-script-studio
+  root: ./youtube-script-studio-workspace
+
+defaults:
+  capture: none              # tightened per agent (pane for gemini/hermes)
+  can_talk_to: []            # tightened per agent below
+
+agents:
+  - name: producer
+    type: claude
+    workdir: "{root}/repo"
+    can_talk_to: [researcher, scriptwriter, metadata_writer, user]
+    command: "claude --dangerously-skip-permissions"
+    capture: none
+    role: |
+      You are the PRODUCER, the hub of a YouTube video studio. You turn the
+      user's topic into a publish-ready package and are the ONLY agent who talks
+      to the user. You do not write the script yourself; you set the angle,
+      audience, target length, and the promise of the video, then coordinate.
+      Your team: researcher (hook ideas + retention/pacing patterns for this
+      topic), scriptwriter (writes the full script), metadata_writer (title
+      options, thumbnail copy, description, tags, chapter markers).
+      Run it like this: (1) restate the topic as a one-paragraph brief -- angle,
+      audience, length, the single promise -- and send it to the researcher
+      first; (2) pass the research to the scriptwriter to draft the script;
+      (3) have the metadata_writer build titles/thumbnail/description/tags/
+      chapters against the FINAL script; (4) assemble everything and send the
+      finished package to the user.
+      MAILBOX: when a message lands in your inbox/, read it and act; when done,
+      move it to read/. To send, write a file into outbox/<name>/ (read
+      outbox/<name>/about.md first to see who they are and whether they are
+      available) and finish your turn. You may only message the agents in your
+      can_talk_to list.
+
+  - name: researcher
+    type: gemini
+    workdir: "{root}/repo"
+    can_talk_to: [producer]
+    command: "gemini --yolo"
+    capture: pane
+    role: |
+      You are the RESEARCHER. Given the producer's brief, find what makes THIS
+      topic watchable: 3-5 strong hook openers, the questions the audience
+      actually types, the moments where viewers drop off and how to hold them
+      (pattern interrupts, open loops, payoff placement), and any facts or
+      angles worth including. You do not write the script -- you hand the
+      producer a tight research brief they can pass to the scriptwriter. Report
+      only to the producer.
+
+  - name: scriptwriter
+    type: claude
+    workdir: "{root}/repo"
+    can_talk_to: [producer, metadata_writer]
+    command: "claude --dangerously-skip-permissions"
+    capture: none
+    role: |
+      You are the SCRIPTWRITER. Given the producer's brief and the researcher's
+      findings, write the full video SCRIPT.md: a cold-open hook in the first 15
+      seconds, a clear through-line, spoken-word narration (not bullet points),
+      B-roll / on-screen cues in brackets, and a call to action. Match the
+      target length and audience. When the script is solid, send a copy straight
+      to the metadata_writer so titles and chapters track the real script, and
+      report the draft to the producer.
+
+  - name: metadata_writer
+    type: codex
+    workdir: "{root}/repo"
+    can_talk_to: [producer, scriptwriter]
+    command: "codex --yolo"
+    capture: none
+    role: |
+      You are the METADATA_WRITER. Working from the FINAL script, produce the
+      packaging that gets the video found and clicked: 5-8 title options (front-
+      load the keyword, keep them honest), thumbnail copy (2-4 punchy words),
+      an SEO description with the payoff in the first two lines, a tag list, and
+      timestamped chapter markers derived from the script's sections. If the
+      script is missing a section you need for a chapter, ask the scriptwriter
+      directly; deliver the finished packaging to the producer.

package/hooks/claude_stop.sh

@@ -1,16 +1,18 @@
 #!/usr/bin/env bash
 # Claude Code `Stop` hook: fires when Claude finishes responding.
 # Claude passes a JSON payload on stdin containing `transcript_path`.
-# Installed automatically into <agent-workdir>/.claude/settings.json by `agentainer up`.
+# Installed automatically into <agent-workdir>/.claude/settings.json by
+# `agentainer up`.
 #
 # A hook must never break the agent it is attached to, so every failure here is
 # swallowed and the script always exits 0.
+set -uo pipefail
 
 HERE="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
 
 log="/dev/null"
-if [[ -n "${SWARM_ROOT:-}" ]] && mkdir -p "$SWARM_ROOT/.swarm/logs" 2>/dev/null; then
-  log="$SWARM_ROOT/.swarm/logs/hooks.log"
+if [[ -n "${AGENTAINER_ROOT:-}" ]] && mkdir -p "$AGENTAINER_ROOT/.agentainer/logs" 2>/dev/null; then
+  log="$AGENTAINER_ROOT/.agentainer/logs/hooks.log"
 fi
 
 "$HERE/agentainer" hook claude >>"$log" 2>&1

package/hooks/codex_notify.sh

@@ -1,15 +1,16 @@
 #!/usr/bin/env bash
 # Codex `notify` program: codex invokes it with a JSON payload as $1 whenever a
 # turn completes (payload type: "agent-turn-complete", with last-assistant-message).
-# Wired up via <agent-workdir>/.codex/config.toml + CODEX_HOME by `swarm up`.
+# Wired up via <agent-workdir>/.codex/config.toml + CODEX_HOME by `agentainer up`.
 #
 # Always exits 0 so a hook failure can never disturb the agent.
+set -uo pipefail
 
 HERE="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
 
 log="/dev/null"
-if [[ -n "${SWARM_ROOT:-}" ]] && mkdir -p "$SWARM_ROOT/.swarm/logs" 2>/dev/null; then
-  log="$SWARM_ROOT/.swarm/logs/hooks.log"
+if [[ -n "${AGENTAINER_ROOT:-}" ]] && mkdir -p "$AGENTAINER_ROOT/.agentainer/logs" 2>/dev/null; then
+  log="$AGENTAINER_ROOT/.agentainer/logs/hooks.log"
 fi
 
 "$HERE/agentainer" hook codex "${1:-}" >>"$log" 2>&1