anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

feature request: ability to configure which file will contain agent rules #421

New Issue
Closed
opened 2026-02-16 17:26:40 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 17:26:40 -05:00
Owner
Copy Link
Copy Source

Originally created by @rekram1-node on GitHub (Jul 1, 2025).

Originally assigned to: @thdxr on GitHub.

At my company we use a variety of llm tooling and we need to be able to have rule standards used across all of these tools, I feel like instead of extending the following in packages/opencode/src/session/system.ts:

  const CUSTOM_FILES = [
    "AGENTS.md",
    "CLAUDE.md",
    "CONTEXT.md", // deprecated
  ]

We could allow a user to override / extend this in their configuration potentially?

I realize during the /init we can do most of this but I don't wanna rerun that every time someone updates one of the rules (nor do I wanna copy it in haha)

If this is something that seems reasonable I am happy to open a PR.

Originally created by @rekram1-node on GitHub (Jul 1, 2025). Originally assigned to: @thdxr on GitHub. At my company we use a variety of llm tooling and we need to be able to have rule standards used across all of these tools, I feel like instead of extending the following in `packages/opencode/src/session/system.ts`: ```ts const CUSTOM_FILES = [ "AGENTS.md", "CLAUDE.md", "CONTEXT.md", // deprecated ] ``` We could allow a user to override / extend this in their configuration potentially? I realize during the /init we can do most of this but I don't wanna rerun that every time someone updates one of the rules (nor do I wanna copy it in haha) If this is something that seems reasonable I am happy to open a PR.
yindo closed this issue 2026-02-16 17:26:40 -05:00
yindo commented 2026-02-16 17:26:40 -05:00
Author
Owner
Copy Link
Copy Source

@thdxr commented on GitHub (Jul 1, 2025):

this makes sense - maybe add a set of filenames to a new config key called instructions: […]?

would take a PR

@thdxr commented on GitHub (Jul 1, 2025): this makes sense - maybe add a set of filenames to a new config key called `instructions: […]`?<br><br>would take a PR
yindo commented 2026-02-16 17:26:40 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Jul 2, 2025):

sweet, will do

@rekram1-node commented on GitHub (Jul 2, 2025): sweet, will do
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#421
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?