ArcFlare 1.1: 3D meshes, your session from anywhere, and updates that work offline

ArcFlare started as a way to run language models on your own GPU. 1.1 adds three things that have nothing to do with tokens.

A photo in, a mesh out

That writes chair-hunyuan3d-2mini.glb next to the photo. Five models are supported: Hunyuan3D-2 mini (and its 5-step turbo variant), Hunyuan3D-2 with texturing, Hunyuan3D-2.1, and TripoSR for instant rough drafts.

They are PyTorch pipelines, not GGUFs, so there is no llama.cpp to drive. ArcFlare does the same job it does for llama-server: it finds the pieces, checks them honestly, and supervises a worker process. Setup ends by importing the model's code on your actual device and naming whatever is missing, instead of letting you find out ten minutes into a run.

Torch is the one thing it will not guess. The right wheel depends on your GPU, and on Windows with an AMD card there is no official one at all. So --torch-from <python> borrows a working GPU torch from another environment, read-only, without writing a byte into it.

The agent gets it too. generate_3d is a machine-server tool, so "make me a low-poly lamp and put it in the scene" can now be a real request.

/rc

Type /rc in arcflare agent or arcflare run and you get a key and a link. Open the link on your phone and you are in the session: the output streams in as it is written, and what you type there goes straight to the model on your desk.

• Outbound only. Your machine polls the relay. Nothing listens on a port, so it works behind NAT, a firewall or hotel Wi-Fi.
• The key is a password. It has 192 random bits. The relay stores only a hash, and the link keeps the key in the URL fragment, which a browser never sends.
• Approval follows the person. When a message came from your phone, the agent asks your phone before it runs a command. Nobody answering means no.

The key stays the same between sessions, so your phone reconnects by itself. arcflare rc rotate cuts every device off at once.

/update, online or not

ArcFlare now checks for updates in the background, at most twice a day, and tells you in one line. /update installs it.

Offline, the check fails without a word. And because ArcFlare has no dependencies, one tarball is the whole program:

Make it on a connected machine, carry it over on a stick, install it. Nothing in that path touches a registry.

Everything is in the docs.