feat(t3code-bin): add T3 Code desktop from the AUR
T3 Code is an open-source control plane for coding agents — Claude Code, Codex, OpenCode, Cursor and Grok driven from one desktop app, on the user's own subscriptions. Upstream ships a Linux x86_64 AppImage only, and the AUR's t3code-bin already tracks it, so this syncs from there in the fast ring.
One Omarchy patch: the AUR launcher runs Electron with --no-sandbox. Chromium falls back to a user-namespace sandbox when it finds no setuid helper, which is what happens on Arch, so the flag only turns the sandbox off. Verified both ways against the built package — sandboxed it reaches display setup, and only with namespaces restricted does it abort on the setuid helper.
🤖 Generated by Opus 5 in Claude Code.
This commit is contained in:
1 parent
c2b3796ad9
commit
ab154a00dd
6 files changed
+167
No files matched your search
@@ -0,0 +1,5 @@
|
||||
{
|
||||
"source": "aur",
|
||||
"release_ring": "fast",
|
||||
"upstream_commit": "4f0b415dccf7e3b0b85e2289e8c3a7c8603e9fb4"
|
||||
}
|
||||
@@ -0,0 +1,13 @@
|
||||
--- a/PKGBUILD
|
||||
+++ b/PKGBUILD
|
||||
@@ -96,7 +96,9 @@
|
||||
extra_flags+=(--ozone-platform-hint=auto)
|
||||
fi
|
||||
|
||||
-exec "$appdir/t3code" --no-sandbox "${extra_flags[@]}" "$@"
|
||||
+# Omarchy: Chromium sandboxes itself with a user namespace when it cannot find a
|
||||
+# setuid helper, which is the case on Arch, so --no-sandbox buys nothing here.
|
||||
+exec "$appdir/t3code" "${extra_flags[@]}" "$@"
|
||||
EOF
|
||||
|
||||
ln -s t3code "$pkgdir/usr/bin/t3-code-desktop"
|
||||
Reference in new issue
Block a user