From cc662c37fd59492640ce810dbd8d90f3a065f33a Mon Sep 17 00:00:00 2001 From: Deepak Singh Date: Sun, 29 Mar 2026 08:05:02 +0000 Subject: [PATCH 1/3] docs: cleanup Cursor references in README (closes #3) --- README.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index a9d3e27..2c91bcf 100644 --- a/README.md +++ b/README.md @@ -1,10 +1,10 @@ -# Cursor AI - Building a restrictive Flatpak +# T3 Code - Building a restrictive Flatpak This repository contains the necessary files and automation to build a -restrictive, sandboxed Flatpak for the [Cursor AI](https://cursor.sh/) code +restrictive, sandboxed Flatpak for the [T3 Code](https://t3.chat/) code editor. -The primary goal is to provide a secure environment for running Cursor by +The primary goal is to provide a secure environment for running T3 Code by limiting its access to the host system. The build process is automated with a `Makefile`, requiring only the version number and download URL for a new release to build and package it. @@ -39,13 +39,13 @@ This repository contains the following files: - **`Makefile`**: The main script that automates the entire download, build, and installation process. -- **`com.cursor.App.yml`**: The Flatpak manifest. This is the core blueprint +- **`codes.t3.app.yml`**: The Flatpak manifest. This is the core blueprint that tells `flatpak-builder` how to construct the application, including its dependencies, sources, and sandbox permissions. -- **`com.cursor.App.appdata.xml`**: AppStream metadata for the application. This +- **`codes.t3.app.appdata.xml`**: AppStream metadata for the application. This file provides the information (name, description, version history) that software centers like GNOME Software and KDE Discover use to display the application. -- **`com.cursor.App.desktop`**: The `.desktop` file that allows the application +- **`codes.t3.app.desktop`**: The `.desktop` file that allows the application to be launched from your desktop environment's application menu. ## How to Build @@ -53,19 +53,19 @@ to be launched from your desktop environment's application menu. The build process is managed entirely by the `Makefile`. 1. **Find the Release URL and Version:** -Go to the [Cursor Download History](https://github.com/oslook/cursor-ai-downloads) +Go to the [T3 Code Download History](https://github.com/oslook/t3-code-downloads) or the official website to find the download URL for the Linux AppImage of the version you want to package. 2. **Run the Build Command:** From the root of this project directory, run the `make` command, providing -the `VERSION` and `CURSOR_URL` as arguments. +the `VERSION` and `T3_URL` as arguments. **Example:** ```bash make build VERSION=x.y.z - CURSOR_URL="URL_FOR_XYZ_RELEASE_OBTAINED_FROM_WEBSITE" + T3_URL="URL_FOR_XYZ_RELEASE_OBTAINED_FROM_WEBSITE" ``` This command will: @@ -94,7 +94,7 @@ Once installed, you can normally run your application with: The `Makefile` provides several convenient targets: - `make build`: Downloads the AppImage and builds the Flatpak. (Requires -`VERSION` and `CURSOR_URL`). +`VERSION` and `T3_URL`). - `make install`: Installs the locally built Flatpak for the current user. - `make run`: Runs the installed Flatpak application. - `make uninstall`: Removes the Flatpak from your system. @@ -112,7 +112,7 @@ For easy, on-the-fly permission management *without* rebuilding, you can use flatpak install flathub com.github.tchx84.Flatseal ``` -2. **Launch Flatseal** and select "Cursor" from the list of applications. +2. **Launch Flatseal** and select "T3 Code" from the list of applications. 3. You can now toggle permissions for filesystem access, network sockets, device access, and more. Changes are applied instantly. From ae9cf3819dbc2b7ba6a44bb781dc449c9524efe8 Mon Sep 17 00:00:00 2001 From: Deepak Singh Date: Sun, 29 Mar 2026 18:03:40 +0000 Subject: [PATCH 2/3] fix: update Makefile to use T3_URL and T3-Code target naming --- Makefile | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/Makefile b/Makefile index e7014d8..2fb6a20 100644 --- a/Makefile +++ b/Makefile @@ -1,4 +1,4 @@ -# Makefile for building the Cursor Flatpak +# Makefile for building the T3 Code Flatpak # --- Variables --- APP_ID := codes.t3.app @@ -10,7 +10,7 @@ SQUASHFS_ROOT := squashfs-root ARCH ?= x86_64 -APPIMAGE_FILE = $(notdir $(CURSOR_URL)) +APPIMAGE_FILE = $(notdir $(T3_URL)) .PHONY: all build install run clean uninstall @@ -19,6 +19,7 @@ APPIMAGE_FILE = $(notdir $(CURSOR_URL)) all: build # Builds the Flatpak. Depends on the AppImage being extracted. +build: $(SQUASHFS_ROOT) @echo "--> Building the Flatpak..." # Update the version in the appdata file before building flatpak-builder $(BUILD_DIR) $(MANIFEST) --force-clean @@ -32,7 +33,7 @@ install: build # Uninstalls the application. uninstall: - @echo "--> Uninstalling Cursor..." + @echo "--> Uninstalling T3 Code..." flatpak uninstall $(APP_ID) # --- Helper Targets --- @@ -40,14 +41,14 @@ uninstall: # This target handles downloading and extracting the AppImage. # It's triggered by the 'build' target. -Cursor-$(VERSION)-$(ARCH).AppImage: +T3-Code-$(VERSION)-$(ARCH).AppImage: @echo "--> Preparing AppImage..." - @echo " Downloading from: $(CURSOR_URL)" - wget -O $(APPIMAGE_FILE) "$(CURSOR_URL)" + @echo " Downloading from: $(T3_URL)" + wget -O $(APPIMAGE_FILE) "$(T3_URL)" @echo " Making executable..." chmod +x $(APPIMAGE_FILE) -$(SQUASHFS_ROOT): Cursor-$(VERSION)-$(ARCH).AppImage +$(SQUASHFS_ROOT): T3-Code-$(VERSION)-$(ARCH).AppImage @echo " Extracting AppImage..." ./$(APPIMAGE_FILE) --appimage-extract @echo " Extraction complete. Extracted to '$(SQUASHFS_ROOT)'." From 442a98de00265ab1a4d98fe7a4226682d419618c Mon Sep 17 00:00:00 2001 From: Deepak Singh Date: Sun, 5 Apr 2026 18:03:53 +0000 Subject: [PATCH 3/3] docs: use official T3 Code URL and fix Makefile example in README --- README.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 2c91bcf..d56049c 100644 --- a/README.md +++ b/README.md @@ -53,9 +53,8 @@ to be launched from your desktop environment's application menu. The build process is managed entirely by the `Makefile`. 1. **Find the Release URL and Version:** -Go to the [T3 Code Download History](https://github.com/oslook/t3-code-downloads) -or the official website to find the download URL for the Linux AppImage of the -version you want to package. ++Go to the [T3 Code website](https://t3.chat/) to find the download URL for the ++Linux AppImage of the version you want to package. 2. **Run the Build Command:** From the root of this project directory, run the `make` command, providing @@ -64,8 +63,7 @@ the `VERSION` and `T3_URL` as arguments. **Example:** ```bash - make build VERSION=x.y.z - T3_URL="URL_FOR_XYZ_RELEASE_OBTAINED_FROM_WEBSITE" + make build VERSION=x.y.z T3_URL="URL_FOR_XYZ_RELEASE_OBTAINED_FROM_WEBSITE" ``` This command will: @@ -94,7 +92,7 @@ Once installed, you can normally run your application with: The `Makefile` provides several convenient targets: - `make build`: Downloads the AppImage and builds the Flatpak. (Requires -`VERSION` and `T3_URL`). + `VERSION` and `T3_URL`). - `make install`: Installs the locally built Flatpak for the current user. - `make run`: Runs the installed Flatpak application. - `make uninstall`: Removes the Flatpak from your system.