Repository navigation
[Feature]: On a task page, link document paths written in Context and Agent criteria, not only in Human criterion steps #91
Description
Problem
On /tasks/T-XXX, a path to a project document becomes a link in two cases only:
- the file is named
docs/reports/T-XXX-*.md(listed automatically as a research artifact); - the path is written in the
**Steps:**,**Expected:**or**If not:**of a### Humancriterion.
The same path written in ## Context, in an ### Agent criterion or in the task description is shown as plain text. In web/blueprints/tasks.py, _auto_link_files is called from _render_md_inline and _render_md_block (lines 385 and 401), which are applied to the parsed Human criteria; the rest of the task body is shown as raw Markdown source.
Consequence observed in one project: of 24 documents, 10 were reachable from a task page and 14 were not, although 8 of those 14 were cited in a task file. To attach them, the agent added nine ### Human criteria of the form "open this note and confirm it". Some of these criteria exist mainly to carry a link, which adds review boxes for the operator and dilutes the meaning of a Human criterion.
Proposed Solution
Apply the same existence-gated path linking to ## Context and to ### Agent criteria.
Or add an explicit field, for example a documents: list in the task frontmatter, rendered as a "Documents" block on the task page next to the automatic research artifacts.
Subsystem
Watchtower (Web UI)
Scope
Small (single file, <1 hour)
Alternatives Considered
- Naming every document
docs/reports/T-XXX-*.md: works for research notes, not for deliverables that keep their own name and directory. - Writing a Human criterion for each document: this is the workaround in use; it works but multiplies review boxes.
Additional Context
Version: 1.8.6 (1ea1044), vendored consumer. First seen on 1.8.3; web/blueprints/tasks.py is byte-identical between the versions. Checked again on a served task page of 1.8.6: a path written in ## Context has no href.
Activity
DimitriGeelen commentedon Oct 10, 2026
[AEF intake] Received — 2026-10-10
Thank you. This issue has been ingested into the Agentic Engineering Framework's intake as INTAKE-0007. Next step: classification (type, affected area, severity, whether it reproduces on the current release and on bleeding-edge). You will get a comment here at each step: classified → decision → in progress → fixed on bleeding-edge → available for testing → released.
These status updates are automated, but Dimitri personally looks at every issue and decides what happens to it. Replies on this issue are read.
DimitriGeelen commentedon Oct 10, 2026
[AEF intake] Classified — 2026-10-10
[AEF intake] Accepted — 2026-10-10
Tracked as T-4044, prioritised (horizon: now). Next update here: in progress.
These status updates are automated, but Dimitri personally looks at every issue and decides what happens to it. Replies on this issue are read.
T-4044: scope GitHub #91 (doc-path links in Context/Agent criteria) a…
T-4044: link file paths in task description, Context and Agent criter…
DimitriGeelen commentedon Oct 11, 2026
[AEF intake] Fixed on bleeding-edge — 2026-10-11
Implemented under T-4044 in commit 02f86b0 (on the
bleeding-edgebranch; not yet in a release). We took your first proposal: the same existence-gated path linking now applies to the task description,## Contextand### Agentcriteria, not only to Human criteria. No new frontmatter field./file/<path>; a path to nothing stays plain text, as before.<script>in Context is shown as text, not run); code spans are not double-linked.Regression test
tests/web/test_t4044_task_page_doc_links.py: 6 pass, 3 fail on the old code (Context, Agent, description). Running on our own Watchtower now; the maintainer's visual check is pending.To test it before the release:
git clone -b bleeding-edge https://github.com/DimitriGeelen/agentic-engineering-framework.git aef-be && aef-be/bin/fw upgrade /path/to/your/project, thenfw watchtower restartand open a task whose Context cites a document. Feedback here is welcome. Next update here: released.These status updates are automated, but Dimitri personally looks at every issue and decides what happens to it. Replies on this issue are read.
MikeEchoVoid commentedon Oct 18, 2026
Confirmed fixed on 1.8.11 (e42aa41). On five task pages,
docs/reports/...paths cited in## Context(not only in Human AC steps) are now rendered as/file/...links. Thank you.DimitriGeelen commentedon Oct 18, 2026
[AEF intake] Released — 2026-10-18
T-4044 is released in v1.8.11.
Please confirm it fixes this for you. Reply here if it does not. With no reply in 14 days this issue is closed with a note, and you can reopen it.
How it was tested:
tests/web/test_t4044_task_page_doc_links.py(6 tests: a path in Context, an Agent criterion or the description links to an existing file). Green on bleeding-edge.Why it is released now: v1.8.11 passed the full-suite comparison (https://github.com/DimitriGeelen/agentic-engineering-framework/blob/50fae848ff46e156c1be630e85b0644aa070be38/docs/reports/T-4246-full-suite-comparison.md) and the operator's release decision.
Field evidence: none. The visual check awaits the maintainer's review. Please confirm this works for you.
Release: https://github.com/DimitriGeelen/agentic-engineering-framework/releases/tag/v1.8.11 · Field report: https://github.com/DimitriGeelen/agentic-engineering-framework/blob/50fae848ff46e156c1be630e85b0644aa070be38/docs/reports/field-test-v1.8.11-results.md
These status updates are automated, but Dimitri personally looks at every issue and decides what happens to it. Replies on this issue are read.