Codync
A free, open-source 1:1 alternative to Grok Bot and Muse. Message Claude Code, Codex, Cursor and 40+ coding agents as persistent bots from your iPhone, Mac or Linux desktop. Group chats, threads, appr
Secure, ephemeral, high-performance, low-cost runners within the privacy of your own VPC.
Developer toolsShell · BatchfileGitHub @sprinters-shOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Sprinters Docker image
Translation pending
Taken from the repository README
Loading the full README.
Read the full README ↗Sprinters Docker images
Both Dockerfiles run the scripts in images/build, which wrap GitHub's
runner-images scripts, and are split into stages that BuildKit builds in parallel:
prepared, system-1, java and system-2 install everything that changes shared state, such as packages, users and
profiles. They must run one after another, in the order of GitHub's runner images.tool.sh. Each tool
is listed in tools.txt, together with the image variants that exclude it.build merges the tools into the image with merge.sh, installs the toolcache, and finalizes and cleans up.tool.sh exports what an installer added, and fails the build if it did more than adding files below /usr and /opt
or setting environment variables (apart from PATH). Such installers belong in one of the system stages.
To add a tool, list it in tools.txt, add a stage that runs tool.sh <name> to the Dockerfiles, and mount that stage
in the build stage. A single stage can be built with --target, for example
docker build -f images/Dockerfile-ubuntu-24.04 --target pypy images.
MIT License
Copyright (c) 2026 InfrastructureX GmbH
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.