Skip to content

Let writer tools replace a conversation directory - #280

Closed
nishu-builder wants to merge 1 commit into
codex/git-tree-tools-20260924-70793dfrom
codex/repository-writers-20260924-70793d
Closed

nishu-builder wants to merge 1 commit into
codex/git-tree-tools-20260924-70793dfrom
codex/repository-writers-20260924-70793d

Conversation

@nishu-builder

@nishu-builder nishu-builder commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

A writer can run with scope="feature", receive only that directory, and return its replacement. This lets a tool update several stack gitlinks together without receiving the whole conversation.

The result uses the existing writer proposal path. A concurrent change inside the directory rejects the replacement; edits elsewhere are preserved. Conversation metadata stays outside the worker’s cache key.

@nishu-builder
nishu-builder added this pull request to stack #283 September 24, 2026 02:11
@nishu-builder
nishu-builder force-pushed the codex/repository-writers-20260924-70793d branch from 38d91ab to 83e1907 Compare September 24, 2026 17:45

@nishu-builder nishu-builder left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Parsimony review. The main suggestion is to scope a writer's in and proposal to the declared subtree and keep the clock out of writer-context. That removes the out-of-scope diff, makes writer calls cacheable, and removes the SPEC exception for writers defined inside a source gitlink. Separately: could writers reuse the existing proposal apply path with a strict mode, instead of adding a second one? Details inline.


Generated by Claude Code

Comment thread std/llm-step/src/writers.rs Outdated
Comment thread std/llm-step/src/writers.rs Outdated
Comment thread std/llm-step/src/tools.rs Outdated
Comment thread std/llm-step/src/writers.rs Outdated
@nishu-builder
nishu-builder force-pushed the codex/repository-writers-20260924-70793d branch from 83e1907 to 2fb0dab Compare September 25, 2026 06:02
@nishu-builder nishu-builder changed the title Let repository tools propose conversation edits Let writer tools replace a conversation directory Sep 25, 2026

Copy link
Copy Markdown
Contributor Author

Closing with the replay stack (#282). Its reason for existing was letting the replay tool rewrite a feature directory's gitlinks, and main handles stacks differently now (#291, #293, #296). Ref and writer permissions are being reworked separately in #298.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant