Let the agent file issues from conversation (later addition)
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m17s

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE
This commit is contained in:
dongarandClaude Opus 5.5 committed 2026-10-02 18:26:58 +00:00
1 parent cd2ff6d769
commit acf7ce191c
1 file changed
+11 -1
+11 -1
View File
@@ -816,6 +816,16 @@ request to mean, how it fits the architecture, and its first step. Then:
**Finishing.** The final PR closes the issue on merge; the agent closes the work
item, after checking what is left open (D5).
**Filing issues from conversation** (a later addition, not needed at first). In any
conversation, the agent may file an issue against any project where `dev-agent` is
a collaborator, when the operator asks or agrees to its suggestion.
- **Never self-assigned:** a filed issue is backlog until the operator assigns it,
so the agent can't create work for itself.
- **Duplicates first:** it searches the project's open issues and offers to add to
an existing one instead.
- **Provenance:** the issue says it was filed from a conversation, when, and with
whom, quoting what prompted it.
### D2. Documents are the workflow
The project's own documents live in its repository and carry its design forward:
@@ -955,7 +965,7 @@ a corrupt `.pyc`.
| Class | Examples |
|---|---|
| 1 | Reading the repo, running tests and builds in the workspace or a test container, querying Gitea |
| 2 (in scope) | Editing the workspace, committing to milestone branches, pushing them, opening and updating PRs, commenting on its issues and PRs, cleaning caches, installing project dependencies, packages and toolchains on the project's build VM |
| 2 (in scope) | Editing the workspace, committing to milestone branches, pushing them, opening and updating PRs, commenting on its issues and PRs, filing issues the operator asked for or agreed to (D1), cleaning caches, installing project dependencies, packages and toolchains on the project's build VM |
| 3 | Merging to the default branch (unless the trust dial allows), deleting remote branches or others' work, changing repository settings, anything outside the work item's repo or its project's build VM |
Its scope source is the assigned issue and what was agreed in its conversation