~bigbes/agents-dev · parade

main · last commit 13 days ago · 7g0stsfu

← Back to the parade

ah-0ge Stage 4: agent tools API, question loop, AgentsView links epic Past Stand

status: closed P3 epic
bd reopen ah-0ge
Created byEugene Blikh
Ownerbigbes@gmail.com
Created2026-07-12T23:36:29Z
Updated2026-07-18T17:03:58Z
Closed2026-07-18T17:03:58Z
Description
Per SPEC SS14.4: per-task bearer tokens; ahub tool task-create/ask-user/memory-search/memory-add over loopback HTTP; server-side policies (Triage-only, gen<=2, per-session caps, dedup, project allowlist); question.json -> Question bucket -> comment-answer -> pi --session resume as new attempt; parent auto-Block/unblock on subtask completion; AgentsView: pg push from runner host + /sessions/<id> deep links in comments.
Notes
STATUS 2026-07-17. The FILE-CHANNEL agent capabilities of Stage 4 are DONE and committed (9ec9418, 5ad253a): task-create (ah-0ge.1), parent block/unblock join + pi-session-style resume (ah-0ge.2/.3), ask-user question loop (ah-0ge.4). These use .task/*.json + board state instead of the per-task-bearer-token ahub-tool-over-HTTP API, which the file channel makes optional for the 'agent stops then resumes' pattern.

REMAINING epic scope is infra/external-service gated and NOT autonomously completable by me:
- memory search/add tools -> depend on Stage 3 mem0 (ah-ydx); mem0 REST client is unverifiable without a live mem0 instance and I'd be guessing at its API shape.
- AgentsView /sessions/ deep links -> need 'pg push from the runner host' + a deployed AgentsView (ah-k23 infra); the deep-link URL alone is useless without the push.
- per-task bearer tokens + ahub tool CLI-over-HTTP -> an alternative transport to the file channel; only needed for mid-run (not stop-and-resume) tools, and lower value now that the file channel covers task-create + ask-user.

Recommend: keep this epic open for the HTTP-tools-API + AgentsView items, to be done alongside ah-k23 infra.

Subtasks 6 of 6 done

  • ah-0ge.5 — AgentsView: pg push from agent-1 + per-run session deep links in comments P2 closed
  • ah-0ge.1 — Agent-created tasks via .task/tasks.json file channel P3 closed @Eugene Blikh
  • ah-0ge.2 — Parent auto-Block/unblock join on child completion P3 closed @Eugene Blikh
  • ah-0ge.3 — Resume parent via pi --session with child results as a new attempt P3 closed
  • ah-0ge.4 — Ask-user question loop via .task/question.json file channel P3 closed
  • ah-0ge.6 — HTTP tools API: per-task bearer tokens + ahub tool CLI over loopback P3 closed @Eugene Blikh

Depends on

No outgoing dependencies.

Depended on by

  • ah-0ge.5 — AgentsView: pg push from agent-1 + per-run session deep links in comments parent-child
  • ah-0ge.3 — Resume parent via pi --session with child results as a new attempt parent-child
  • ah-0ge.6 — HTTP tools API: per-task bearer tokens + ahub tool CLI over loopback parent-child
  • ah-0ge.4 — Ask-user question loop via .task/question.json file channel parent-child
  • ah-0ge.1 — Agent-created tasks via .task/tasks.json file channel parent-child
  • ah-0ge.2 — Parent auto-Block/unblock join on child completion parent-child

Unblocks — everything waiting on this, transitively

  • ah-0ge.5 — AgentsView: pg push from agent-1 + per-run session deep links in comments parent-child closed
  • ah-0ge.3 — Resume parent via pi --session with child results as a new attempt parent-child closed
  • ah-0ge.6 — HTTP tools API: per-task bearer tokens + ahub tool CLI over loopback parent-child closed
  • ah-0ge.4 — Ask-user question loop via .task/question.json file channel parent-child closed
  • ah-0ge.1 — Agent-created tasks via .task/tasks.json file channel parent-child closed
  • ah-0ge.2 — Parent auto-Block/unblock join on child completion blocks closed

No comments.

Close reason

All 6 children done: file-channel tools (.1-.4), AgentsView pipeline + deep links (.5), HTTP tools API (.6). Stage 4 complete pending live rollout smoke.
  • Eugene Blikh created the issue · 2026-07-13T02:36:29Z
  • Eugene Blikh added subtask ah-0ge.1 · 2026-07-17T17:38:02Z
  • Eugene Blikh added subtask ah-0ge.2 · 2026-07-17T17:38:02Z
  • Eugene Blikh added subtask ah-0ge.3 · 2026-07-17T17:38:03Z
  • Eugene Blikh added subtask ah-0ge.4 · 2026-07-17T23:14:02Z
  • Eugene Blikh updated notes to STATUS 2026-07-17. The FILE-CHANNEL agent capabilities of Stage 4 are DONE and committed (9ec9418, 5ad253a): task-create (ah-0ge.1), parent block/unblock join + pi-session-style resume (ah-0ge.2/.3), ask-user question loop (ah-0ge.4). These use .task/*.json + board state instead of the per-task-bearer-token ahub-tool-over-HTTP API, which the file channel makes optional for the 'agent stops then resumes' pattern. REMAINING epic scope is infra/external-service gated and NOT autonomously completable by me: - memory search/add tools -> depend on Stage 3 mem0 (ah-ydx); mem0 REST client is unverifiable without a live mem0 instance and I'd be guessing at its API shape. - AgentsView /sessions/ deep links -> need 'pg push from the runner host' + a deployed AgentsView (ah-k23 infra); the deep-link URL alone is useless without the push. - per-task bearer tokens + ahub tool CLI-over-HTTP -> an alternative transport to the file channel; only needed for mid-run (not stop-and-resume) tools, and lower value now that the file channel covers task-create + ask-user. Recommend: keep this epic open for the HTTP-tools-API + AgentsView items, to be done alongside ah-k23 infra. · 2026-07-17T23:14:02Z
  • Eugene Blikh added subtask ah-0ge.5 · 2026-07-18T16:23:54Z
  • Eugene Blikh added subtask ah-0ge.6 · 2026-07-18T16:23:54Z
  • Eugene Blikh closed the issue · 2026-07-18T20:03:58Z
    All 6 children done: file-channel tools (.1-.4), AgentsView pipeline + deep links (.5), HTTP tools API (.6). Stage 4 complete pending live rollout smoke.
  • Eugene Blikh added label milestone:stage-4 · 2026-07-20T03:08:47Z
  • Eugene Blikh removed label milestone:stage-4 · 2026-07-20T03:10:28Z
Stored rows — what this pane was built from, as read
issues 1 row
id ah-0ge
content_hash 2c909b097105e578055b7ee05ca088aa4e70e7f293e15e7aae83f28ef1a5aeda
title Stage 4: agent tools API, question loop, AgentsView links
description Per SPEC SS14.4: per-task bearer tokens; ahub tool task-create/ask-user/memory-search/memory-add over loopback HTTP; server-side policies (Triage-only, gen<=2, per-session caps, dedup, project allowlist); question.json -> Question bucket -> comment-answer -> pi --session resume as new attempt; parent auto-Block/unblock on subtask completion; AgentsView: pg push from runner host + /sessions/<id> deep links in comments.
design
acceptance_criteria
notes STATUS 2026-07-17. The FILE-CHANNEL agent capabilities of Stage 4 are DONE and committed (9ec9418, 5ad253a): task-create (ah-0ge.1), parent block/unblock join + pi-session-style resume (ah-0ge.2/.3), ask-user question loop (ah-0ge.4). These use .task/*.json + board state instead of the per-task-bearer-token ahub-tool-over-HTTP API, which the file channel makes optional for the 'agent stops then resumes' pattern. REMAINING epic scope is infra/external-service gated and NOT autonomously completable by me: - memory search/add tools -> depend on Stage 3 mem0 (ah-ydx); mem0 REST client is unverifiable without a live mem0 instance and I'd be guessing at its API shape. - AgentsView /sessions/ deep links -> need 'pg push from the runner host' + a deployed AgentsView (ah-k23 infra); the deep-link URL alone is useless without the push. - per-task bearer tokens + ahub tool CLI-over-HTTP -> an alternative transport to the file channel; only needed for mid-run (not stop-and-resume) tools, and lower value now that the file channel covers task-create + ask-user. Recommend: keep this epic open for the HTTP-tools-API + AgentsView items, to be done alongside ah-k23 infra.
status closed
priority 3
issue_type epic
assignee NULL
estimated_minutes NULL
created_at 2026-07-12T23:36:29Z
created_by Eugene Blikh
owner bigbes@gmail.com
updated_at 2026-07-18T17:03:58Z
closed_at 2026-07-18T17:03:58Z
closed_by_session
external_ref NULL
spec_id
compaction_level 0
compacted_at NULL
compacted_at_commit NULL
original_size NULL
sender
ephemeral 0
wisp_type
pinned 0
is_template 0
mol_type
work_type
source_system
metadata �{}
source_repo
close_reason All 6 children done: file-channel tools (.1-.4), AgentsView pipeline + deep links (.5), HTTP tools API (.6). Stage 4 complete pending live rollout smoke.
event_kind
actor
target
payload
await_type
await_id
timeout_ns 0
waiters
hook_bead
role_bead
agent_state
last_activity NULL
role_type
rig
due_at NULL
defer_until NULL
no_history 0
started_at NULL
is_blocked 0
dependencies 6 rows
id 1b1c735e-4af4-5c07-88b5-af36eb29b18a
issue_id ah-0ge.5
type parent-child
created_at 2026-07-18T16:23:54Z
created_by Eugene Blikh
metadata �{}
thread_id
depends_on_issue_id ah-0ge
depends_on_wisp_id NULL
depends_on_external NULL
id 4d47ace9-323a-5735-a20b-fb74dd00831b
issue_id ah-0ge.3
type parent-child
created_at 2026-07-17T17:38:03Z
created_by Eugene Blikh
metadata �{}
thread_id
depends_on_issue_id ah-0ge
depends_on_wisp_id NULL
depends_on_external NULL
id 5b39d31a-32c4-5a8a-a9c2-a81997dbd0d0
issue_id ah-0ge.6
type parent-child
created_at 2026-07-18T16:23:54Z
created_by Eugene Blikh
metadata �{}
thread_id
depends_on_issue_id ah-0ge
depends_on_wisp_id NULL
depends_on_external NULL
id 5e2ed0b3-8cef-593b-a52d-363938a44faf
issue_id ah-0ge.4
type parent-child
created_at 2026-07-17T23:14:02Z
created_by Eugene Blikh
metadata �{}
thread_id
depends_on_issue_id ah-0ge
depends_on_wisp_id NULL
depends_on_external NULL
id 6423d3fb-f348-5e36-9df3-0ff9c07ba03f
issue_id ah-0ge.1
type parent-child
created_at 2026-07-17T17:38:02Z
created_by Eugene Blikh
metadata �{}
thread_id
depends_on_issue_id ah-0ge
depends_on_wisp_id NULL
depends_on_external NULL
id 89451810-b9c9-5774-8dfa-d2150d295f85
issue_id ah-0ge.2
type parent-child
created_at 2026-07-17T17:38:02Z
created_by Eugene Blikh
metadata �{}
thread_id
depends_on_issue_id ah-0ge
depends_on_wisp_id NULL
depends_on_external NULL
events 5 rows
id 019f58b0-7c89-7f0f-b898-f324000256f4
issue_id ah-0ge
event_type created
actor Eugene Blikh
old_value
new_value
comment NULL
created_at 2026-07-13T02:36:29Z
id 019f71b6-f14b-7dd3-a606-c8cdb012792c
issue_id ah-0ge
event_type updated
actor Eugene Blikh
old_value {"id":"ah-0ge","title":"Stage 4: agent tools API, question loop, AgentsView links","description":"Per SPEC SS14.4: per-task bearer tokens; ahub tool task-create/ask-user/memory-search/memory-add over loopback HTTP; server-side policies (Triage-only, gen\u003c=2, per-session caps, dedup, project allowlist); question.json -\u003e Question bucket -\u003e comment-answer -\u003e pi --session resume as new attempt; parent auto-Block/unblock on subtask completion; AgentsView: pg push from runner host + /sessions/\u003cid\u003e deep links in comments.","status":"open","priority":3,"issue_type":"epic","owner":"bigbes@gmail.com","created_at":"2026-07-12T23:36:29Z","created_by":"Eugene Blikh","updated_at":"2026-07-12T23:36:29Z"}
new_value {"notes":"STATUS 2026-07-17. The FILE-CHANNEL agent capabilities of Stage 4 are DONE and committed (9ec9418, 5ad253a): task-create (ah-0ge.1), parent block/unblock join + pi-session-style resume (ah-0ge.2/.3), ask-user question loop (ah-0ge.4). These use .task/*.json + board state instead of the per-task-bearer-token ahub-tool-over-HTTP API, which the file channel makes optional for the 'agent stops then resumes' pattern.\n\nREMAINING epic scope is infra/external-service gated and NOT autonomously completable by me:\n- memory search/add tools -\u003e depend on Stage 3 mem0 (ah-ydx); mem0 REST client is unverifiable without a live mem0 instance and I'd be guessing at its API shape.\n- AgentsView /sessions/ deep links -\u003e need 'pg push from the runner host' + a deployed AgentsView (ah-k23 infra); the deep-link URL alone is useless without the push.\n- per-task bearer tokens + ahub tool CLI-over-HTTP -\u003e an alternative transport to the file channel; only needed for mid-run (not stop-and-resume) tools, and lower value now that the file channel covers task-create + ask-user.\n\nRecommend: keep this epic open for the HTTP-tools-API + AgentsView items, to be done alongside ah-k23 infra."}
comment NULL
created_at 2026-07-17T23:14:02Z
id 019f762f-49ac-7065-b058-8639a8458aeb
issue_id ah-0ge
event_type closed
actor Eugene Blikh
old_value
new_value All 6 children done: file-channel tools (.1-.4), AgentsView pipeline + deep links (.5), HTTP tools API (.6). Stage 4 complete pending live rollout smoke.
comment NULL
created_at 2026-07-18T20:03:58Z
id 019f7cda-94b2-7b71-bfba-47e596676550
issue_id ah-0ge
event_type label_added
actor Eugene Blikh
old_value NULL
new_value NULL
comment Added label: milestone:stage-4
created_at 2026-07-20T03:08:47Z
id 019f7cdc-1d2c-7bb8-8067-bbfef453e1d2
issue_id ah-0ge
event_type label_removed
actor Eugene Blikh
old_value NULL
new_value NULL
comment Removed label: milestone:stage-4
created_at 2026-07-20T03:10:28Z