Open a task's artifact folder from the a modal with f - #420
Merged
Merged
Conversation
The repo-artifact modal (`A`) has had `f` — open the repo's artifact folder in the host's file manager — since repo artifacts landed. The task-artifact modal (`a`) had no equivalent: a task's artifacts could only be opened one file at a time, over REST (`Enter`) or in place (`e`). Add `f` to the task modal, resolving to `<artifacts>/tasks/<task-id>/` via a new `FilesystemArtifactStore.task_artifact_dir` — `path()`'s directory twin, so the layout stays owned by the store. `action_open_folder` moves into the shared `_ArtifactListScreen` base now that both modals bind it; the Dashboard decides which scope's directory it resolves to. The warning differs from the repo modal's deliberately: a task's directory is created with its first artifact, so "nothing written yet" is the ordinary reason there's no folder and gets said plainly, rather than folded into the repo modal's single "isn't on this machine". Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
tildesrc
marked this pull request as ready for review
September 20, 2026 18:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The repo-artifact modal (
A) has hadf— open the repo's artifact folder in the host's file manager — since repo artifacts landed. The task-artifact modal (a) had no equivalent: a task's artifacts could only be opened one file at a time, over REST (Enter) or in place (e).anow reads the same asA:FilesystemArtifactStore.task_artifact_dir—path()'s directory twin, returning<artifacts>/tasks/<task-id>/orNonewhen it isn't here, so the layout stays owned by the store. It's the id-named directory, not thetasks/<slug>alias symlink.action_open_foldermoves into the shared_ArtifactListScreenbase now that both modals bind it; the Dashboard decides which scope's directory the"folder"mode resolves to.mkdir-ed on demand —ctrl+aalready covers adding files.The key lives in the modal rather than on the task table (where
walready opens the task's workdir), keeping the two artifact modals identical.Docs updated:
docs/dashboard.md,docs/tasks.md, the dashboard module docstring, and theAGENTS.md/ARCHITECTURE.mdlines that said only repos had a folder key.Plan: the task's
plan.mdartifact (panopticon://tasks/de75ab7fd77e4c0d8623590174a6a369/artifacts/plan.md).🤖 Generated with Claude Code