Who it is forA privacy-minded developer who does not want to send photos to a hosted image service or manage an OpenAI key.
The problemMost image-to-pet workflows depend on a hosted API key, which adds cost and sends personal photos out of the machine.
The outcomeA companion built on local open-weight neural editing, with the raw references kept on the local machine.
What you need first
- Two or more reference photos of the subject (the README says raw personal references stay local by default)
- A Windows machine for the .bat installers, which the README describes
- Python, the repo language, for the pocketmen CLI
- An NVIDIA GPU with enough VRAM for the neural engine; otherwise PocketMen falls back to the deterministic v0.2 engine
- Codex, if you want to use the $pocketmen-with-you skill
Steps
- Run
INSTALL_SKILL.batto set up the isolated local runtime. - Run
PREPARE_NEURAL_ENGINE.batto cache the default FLUX.2 [klein] 4B model locally. - Run
pocketmen create --reference photo-1.jpg --reference photo-2.jpg --engine neural --backend flux2-klein-4b --quality max, then keep only the installed package for sharing. (inferred, check the README)
Prompt for your agent
Using the repo six-nut/PocketMen-with-you, run `pocketmen create` with --engine neural --backend flux2-klein-4b on the references at <photo-1> and <photo-2>. Expected output: pet.json and spritesheet.webp, with no OPENAI_API_KEY set. Verify that the final package contains only pet.json and spritesheet.webp.
Caveat. The README says the default engine falls back to the v0.2 engine when the GPU or neural runtime is missing, so confirm which engine ran before assuming neural output.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page