Skip to content

[Feature]: Support for a global agent prompt (e.g. ~/.claude/CLAUDE.md) #1233

Closed

Description

@firminunderscore

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I am describing a concrete problem or use case, not just a vague idea.

Area

Not sure

Problem or use case

The ~/.claude/CLAUDE.md file is very useful to prevent Claude from co-authoring itself or telling him how I want him to do things. It works fine when using the Claude CLI directly, but t3code doesn't seems to pick it up. There's no way to have global preferences that apply across all projects without copy-pasting the same file everywhere.
This is based on my experience with Claude specifically, I haven't tested with Codex or other providers, but the concept should be provider-agnostic.

Proposed solution

Import the global prompt file (e.g. ~/.claude/CLAUDE.md or a provider-agnostic ~/.t3code/global-prompt.md) before the project-specific one, so project config can override global defaults. Or have a global prompt option in the user settings that works regardless of the agent provider.

Why this matters

Most of my agent instructions are personal preferences (coding style, interaction patterns, behaviors), not project-specific. Having to duplicate them across every repo is annoying and easy to forget.

Smallest useful scope

Load a single global prompt file and prepend it to the project-level agent prompt before sending to the provider.

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution

  • I would be open to helping implement this.

Activity

  1. added
    enhancementRequested improvement or new capability.
    needs-triageIssue needs maintainer review and initial categorization.
    on Mar 20, 2026
  2. chrisdeeming commented on Apr 8, 2026

    @chrisdeeming
    Contributor

    The ~/.claude/CLAUDE.md file is very useful to prevent Claude from co-authoring itself or telling him how I want him to do things.

    Adding the following to your ~/.claude/settings.json should work and absolutely does when using Claude Code directly.

      "attribution": {
        "commit": ""
      },

    CLAUDE.md is probably valid too.

    All that being said, you're absolutely right that T3 Code isn't reading the settings.json either. So ultimately the same issue but worth noting that pretty much any environment config isn't working as expected.

  3. firminunderscore commented on Apr 9, 2026

    @firminunderscore
    Author

    Okay, thanks. I didn't know that (honestly, I wasn't really looking into it too deeply).
    That's one less thing in my claude.md then

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementRequested improvement or new capability.needs-triageIssue needs maintainer review and initial categorization.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions