Skip to content

Open-source Grok Bot alternative for named AI teammates. Local-first desktop, web, and mobile clients with per-bot tools, instructions, and memory. Independent fork of T3 Code.

docs: route feature requests to Discussions

Julius Marmingee9ae134c59be
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
index 9bc321dac..38a764eab 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -9,6 +9,7 @@ body:
attributes:
value: |
Use this form for broken behavior, regressions, crashes, or reliability problems.
+ Feature requests belong in [Discussions](https://github.com/pingdotgg/t3code/discussions/categories/ideas).
Search existing issues first and keep the report focused on one problem.
- type: checkboxes
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000..4f4940ba6
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+ - name: Feature request
+ url: https://github.com/pingdotgg/t3code/discussions/categories/ideas
+ about: Suggest an improvement or new capability in Discussions.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
deleted file mode 100644
index 3c9424fb3..000000000
--- a/.github/ISSUE_TEMPLATE/feature_request.yml
+++ /dev/null
@@ -1,102 +0,0 @@
-name: Feature request
-description: Propose a scoped improvement or new capability.
-title: "[Feature]: "
-labels:
- - enhancement
- - needs-triage
-body:
- - type: markdown
- attributes:
- value: |
- Use this form for new capabilities or meaningful improvements to existing behavior.
- This repo is still early. Small, concrete requests that clearly explain the problem and scope are much easier to evaluate.
-
- - type: checkboxes
- id: checks
- attributes:
- label: Before submitting
- options:
- - label: I searched existing issues and did not find a duplicate.
- required: true
- - label: I am describing a concrete problem or use case, not just a vague idea.
- required: true
-
- - type: dropdown
- id: area
- attributes:
- label: Area
- description: Which part of the project would this change affect?
- options:
- - apps/web
- - apps/server
- - apps/desktop
- - apps/mobile
- - packages/contracts or packages/shared
- - Build, CI, or release tooling
- - Docs
- - Not sure
- validations:
- required: true
-
- - type: textarea
- id: problem
- attributes:
- label: Problem or use case
- description: What are you trying to do? What is hard, slow, or impossible today?
- placeholder: I want to reconnect to an existing provider session after a browser refresh without losing the current thread state.
- validations:
- required: true
-
- - type: textarea
- id: proposal
- attributes:
- label: Proposed solution
- description: Describe the behavior, API, or UX you want.
- placeholder: Persist enough session metadata so the client can discover and reattach to the active provider session on load.
- validations:
- required: true
-
- - type: textarea
- id: value
- attributes:
- label: Why this matters
- description: Who benefits, and what outcome does this unlock?
- placeholder: This would make reconnects predictable during network drops and reduce accidental duplicate sessions.
- validations:
- required: true
-
- - type: textarea
- id: scope
- attributes:
- label: Smallest useful scope
- description: What is the narrowest version of this request that would still solve your problem?
- placeholder: A first pass only needs to support restoring the active session for the current thread.
- validations:
- required: true
-
- - type: textarea
- id: alternatives
- attributes:
- label: Alternatives considered
- description: Workarounds, prior art, or other approaches you considered.
- placeholder: I currently work around this by manually restarting the provider session, but that loses in-flight context.
-
- - type: textarea
- id: tradeoffs
- attributes:
- label: Risks or tradeoffs
- description: What costs, complexity, or edge cases should be considered?
- placeholder: This may require careful handling when the underlying provider session has already exited.
-
- - type: textarea
- id: references
- attributes:
- label: Examples or references
- description: Links, screenshots, mockups, or comparable tools.
-
- - type: checkboxes
- id: contribution
- attributes:
- label: Contribution
- options:
- - label: I would be open to helping implement this.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8b734a99b..e8e2f9b11 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -4,7 +4,9 @@
We are not actively accepting contributions right now.
-You can still open an issue or PR, but please do so knowing there is a high chance we close it, defer it forever, or never look at it.
+You can still report a bug or open a PR, but please do so knowing there is a high chance we close it, defer it forever, or never look at it.
+
+Feature requests and proposals belong in [Ideas discussions](https://github.com/pingdotgg/t3code/discussions/categories/ideas), not issues.
If that sounds annoying, that is because it is. This project is still early and we are trying to keep scope, quality, and direction under control.
@@ -50,9 +52,9 @@ If the change depends on motion, timing, transitions, or interaction details, in
If we have to guess what changed, we are much less likely to review it.
-## Issues First
+## Discuss Changes First
-If you are thinking about a non-trivial change, open an issue first.
+If you are thinking about a non-trivial change, start a discussion first. Issues are reserved for bug reports.
That still does not mean we will want the PR, but it gives you a chance to avoid wasting your time.
diff --git a/README.md b/README.md
index a7264ef62..8ec101387 100644
--- a/README.md
+++ b/README.md
@@ -113,6 +113,8 @@ Checkout their getting started guide for more information: https://viteplus.dev/
vp i
```
-Read [CONTRIBUTING.md](./CONTRIBUTING.md) before opening an issue or PR.
+Read [CONTRIBUTING.md](./CONTRIBUTING.md) before reporting a bug or opening a PR.
+
+Have a feature request? Start an [Ideas discussion](https://github.com/pingdotgg/t3code/discussions/categories/ideas).
Need support? Join the [Discord](https://discord.gg/jn4EGJjrvv).