Skip to content

docs: align agent instructions with upstream #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tarik02 merged 1 commit into from
Jul 29, 2026
Merged

docs: align agent instructions with upstream #92

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 1 addition & 12 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,18 +4,7 @@ T3 Code is a minimal GUI for coding agents. A Node WebSocket server wraps provid

You can think of T3 Code as an open source "bring-your-own-subscription" alternative to apps like Claude Desktop, Codex App, Cursor Glass and Conductor.

## Fork Notes

- `FORK.md` documents behavior that intentionally differs from upstream.
- When making fork-only changes, update `FORK.md` in the same change so future upstream merges have current context.
- Keep workflow-only fork changes narrow and prefer job-level disables over broad refactors.
- Do not commit package version bumps solely to represent fork releases.
- Keep macOS release signing separate from Apple notarization; do not require notarization secrets just to sign updater artifacts.
- Keep self-signed macOS signing certificate trust in the release workflow when using non-Apple signing certificates.
- Re-check Electron updater channel behavior when changing version strings, release metadata, or desktop packaging.
- Keep fork-only storage in `state-tarik02.sqlite` unless intentionally upstreaming it.
- When preparing fork PRs, branch from `origin/main` and target `tarik02/t3code:main`.
- If a fork PR branch accidentally includes upstream history, rebuild it from `origin/main` and replay only the intended diff.
Fork-specific behavior and maintenance notes are documented in `FORK.md`.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 29, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Preserve the fork maintenance requirements

When an agent makes a fork-only change, this pointer is not an equivalent replacement for the removed instructions: FORK.md inventories current behavior but does not tell the agent to update that inventory, base fork PRs on origin/main, target tarik02/t3code:main, or repair branches containing upstream history. Those workflows therefore lose their only repository-specific safeguards; migrate the still-applicable procedural rules into FORK.md before replacing them with this pointer.

AGENTS.md reference: AGENTS.md:L7-L7

Useful? React with 👍 / 👎.


## What makes T3 Code special?

Expand Down
Loading