# How to Get Support for t3code: Discord, GitHub Issues, and Troubleshooting

> Need support for t3code? Connect with the community on Discord or submit bug reports and feature requests via GitHub Issues for fast troubleshooting and development help.

- Repository: [Ping.gg/t3code](https://github.com/pingdotgg/t3code)
- Tags: support
- Published: 2026-04-18

---

**Join the official Discord server at https://discord.gg/jn4EGJjrvv for real-time community support, or use the structured GitHub issue templates to report bugs and request features.**

t3code is an early-stage monorepo that provides a web-based GUI for AI coding agents like OpenAI Codex and Anthropic Claude. Because the project is under heavy active development, knowing how to get support for t3code efficiently is essential for contributors and users encountering issues.

## Primary Support Channel: The Discord Community

The fastest way to get help is through the **Discord server**. The maintainers use this channel for release announcements, interactive troubleshooting, and architectural discussions.

### Where to Find the Discord Link

The invitation URL appears in two canonical locations within the repository:

- **[`README.md`](https://github.com/pingdotgg/t3code/blob/main/README.md)** (line 62): The primary documentation displays a prominent call-to-action: "Need support? Join the [Discord](https://discord.gg/jn4EGJjrvv)."

- **`apps/marketing/src/layouts/Layout.astro`** (line 55): The public marketing site renders the same invitation in its navigation component, ensuring visitors can find support regardless of which page they land on.

## Reporting Issues on GitHub

For structured bug reports or formal feature requests, use the repository's **issue templates**. This ensures the maintainers receive consistent, actionable information.

### Using Issue Templates

The `.github/ISSUE_TEMPLATE/` directory contains two primary forms:

- **[`bug_report.yml`](https://github.com/pingdotgg/t3code/blob/main/bug_report.yml)**: A structured template that prompts for environment details, reproduction steps, and expected vs. actual behavior.

- **[`feature_request.yml`](https://github.com/pingdotgg/t3code/blob/main/feature_request.yml)**: A template for proposing new functionality, including motivation and potential implementation details.

Using these templates significantly reduces back-and-forth and helps triage issues faster.

### Contribution Guidelines

Before submitting a pull request, consult **[`CONTRIBUTING.md`](https://github.com/pingdotgg/t3code/blob/main/CONTRIBUTING.md)** (lines 53-58). The document specifies that contributors should **open an issue first** to discuss significant changes. This prevents wasted effort on features that may conflict with the project's roadmap.

## Diagnostic Tools and Observability

When debugging complex issues, providing **diagnostic logs** drastically improves support response time.

The repository includes a dedicated **[`docs/observability.md`](https://github.com/pingdotgg/t3code/blob/main/docs/observability.md)** file that explains how to collect structured logs and telemetry. You can generate a diagnostic bundle using the internal logging utilities:

```typescript
// Example: src/utils/log.ts – helper used throughout the repo
import { createWriteStream } from "node:fs";

export function writeDiagnosticLog(filename: string, data: unknown) {
  const stream = createWriteStream(filename, { flags: "a" });
  stream.write(`${new Date().toISOString()} – ${JSON.stringify(data)}\n`);
  stream.end();
}

// Usage during server startup
import { writeDiagnosticLog } from "./utils/log";

writeDiagnosticLog("t3code-debug.log", {
  nodeVersion: process.version,
  platform: process.platform,
  env: process.env.NODE_ENV,
});

```

Attach the resulting `t3code-debug.log` to your Discord message or GitHub issue to give maintainers immediate visibility into your environment.

## Quick Start Commands Before Requesting Help

Ensure you are running the latest version before seeking support. Common commands include:

```bash

# Run t3code without installing

npx t3

# Or install locally and start development (requires bun)

bun install .
bun run dev   # starts both server and web UI

```

If `bun run dev` fails, capture the terminal output and your `t3code-debug.log` file before posting in the support channels.

## Summary

- **Discord** at https://discord.gg/jn4EGJjrvv is the fastest channel for interactive support and community discussion.
- **GitHub Issues** with structured templates provide the best path for formal bug reports and feature requests.
- **Contributing** requires opening an issue first for significant changes, as documented in [`CONTRIBUTING.md`](https://github.com/pingdotgg/t3code/blob/main/CONTRIBUTING.md).
- **Observability** tools in [`docs/observability.md`](https://github.com/pingdotgg/t3code/blob/main/docs/observability.md) help generate diagnostic logs that accelerate troubleshooting.

## Frequently Asked Questions

### Where is the official t3code Discord server?

The official server is located at **https://discord.gg/jn4EGJjrvv**. This link appears in the [`README.md`](https://github.com/pingdotgg/t3code/blob/main/README.md) and in the marketing site layout at `apps/marketing/src/layouts/Layout.astro`.

### How do I report a bug in t3code?

Navigate to the GitHub repository and open a new issue using the **Bug Report template** in [`.github/ISSUE_TEMPLATE/bug_report.yml`](https://github.com/pingdotgg/t3code/blob/main/.github/ISSUE_TEMPLATE/bug_report.yml). Include your environment details, reproduction steps, and attach any relevant diagnostic logs from [`docs/observability.md`](https://github.com/pingdotgg/t3code/blob/main/docs/observability.md).

### Should I open a GitHub issue or ask on Discord first?

For quick questions, troubleshooting help, or clarification on usage, use **Discord** first. For confirmed bugs, crashes, or formal feature requests, use **GitHub Issues** with the appropriate template. If you plan to contribute code, you must open a GitHub issue first per [`CONTRIBUTING.md`](https://github.com/pingdotgg/t3code/blob/main/CONTRIBUTING.md).

### How can I generate diagnostic logs for troubleshooting?

Follow the **Observability** guide in [`docs/observability.md`](https://github.com/pingdotgg/t3code/blob/main/docs/observability.md). You can use the `writeDiagnosticLog` utility shown in the repository to capture your Node.js version, platform, and environment variables into a `t3code-debug.log` file. Attach this file to your support request.