Four public repositories for Adobe-style creative apps collected 3,497 GitHub stars in about a week. MrKeyoor's tracker captured LightCraft at 952 stars, PrintCraft at 883, VectorCraft at 841 and EffectCraft at 821 between 20:20 UTC on October 6 and 00:20 UTC on October 7. The useful part sits below the familiar clone pitch: all four treat the visible interface as one client of a command system that an AI agent can also operate.
GitHub records the first three repositories as created on September 30 and EffectCraft on October 1. Those dates show when these public repositories appeared, not how long their code took to write. Their histories already contain hundreds of commits, and each project belongs to the ArtCraft team's wider collection of Rust creative software. The sudden star count is an attention signal. It does not tell us whether a raw photo, PDF, illustration or motion project will survive a professional round trip.
One command path for the person and the agent
A slider drag in LightCraft, a page operation in PrintCraft and a keyframe edit in EffectCraft all follow the same broad route. The app assigns the action a stable command identifier with JSON parameters. Menus, shortcuts and interface gestures call that command. A CLI, a local control channel and an MCP server can call it too. LightCraft's MCP documentation lists commands for importing photos, changing develop settings, applying presets, rendering images and exporting files. In connected mode, an agent can request a screenshot, inspect widgets and send pointer gestures to the running app.
That design gives an agent more useful handles than screen coordinates alone. It can ask LightCraft for the accepted range of an exposure control, change the value, render the photo and inspect the returned image. EffectCraft exposes project structure, layer properties, keyframes, effects and rendered frames through named tools. A failed batch can roll back as one undo step. The human interface and the automation path still meet at the same engine, which reduces the chance that the agent is manipulating a second, poorer version of the application.
The projects also make different safety choices visible. PrintCraft's automation guide says its MCP server starts only when the user launches it, communicates over standard input and output, and opens no network port. A --root option confines file access to one directory. Its live interface control listens on loopback and requires a random token stored in a user-readable file. Those boundaries matter for an agent that can open, alter and save documents. Undo helps with an editing mistake, but it cannot repair overly broad file access.
This command-first structure is the most reusable work in the four repositories. A developer can use the same engine for a desktop app, a batch job or a test without teaching a model where a button happens to sit today. MCP is one adapter on top. The harder work remains in the command definitions, state model, validation and undo behavior that make automation predictable.
Installers exist, with young version numbers
These repositories ship more than source screenshots. At the time of reporting, LightCraft 0.2.1 and PrintCraft 0.2.1 offered packaged builds for macOS, Windows and several Linux formats, alongside command-line and web bundles. VectorCraft 0.4.0 and EffectCraft 0.4.0 added Windows Arm64 packages. Each release includes a checksum file. Version numbers below 1.0 fit the projects' own warnings about unfinished compatibility.
Rust is doing two jobs here. It supplies the native engines and keeps the core separate from the egui interface, while WebAssembly carries much of the same code into a browser build. PrintCraft describes a layered Cargo workspace for parsing, cryptography, page operations, rendering and automation. Its README reports more than 200 unit, property and interface tests, plus corpus runs against 983 pdf.js files. That is the team's result, not an independent benchmark, but the named corpus and pass counts give outside contributors something specific to reproduce.
The readiness notes matter more than the feature lists
LightCraft has the boldest everyday-use estimate. Its status table puts feature-count parity with Lightroom near 79 percent and core features at 98 percent, then cuts its day-to-day replacement estimate to 60 to 70 percent. The gap comes from work that photographers notice quickly: non-DNG camera colour can look muted, CR3 and some compressed raw formats open only as embedded previews, and AI denoise is absent. The project calls its figures self-assessed.
PrintCraft is blunter about the work curve. Its October status note says about half of Acrobat Pro's offline features are present, including 88 percent of its must-haves, yet estimates that only a third of the work is done because harder tasks remain. Existing-text editing is thin, especially for CJK text. OCR beyond Latin script, long-term signature validation and several archival or print standards are missing. The team also says fuzzing still finds crashes and hangs in hostile files.
VectorCraft estimates that 69 to 75 percent of Illustrator's features work, while only 40 to 55 percent of the experience would be hard for a power user to distinguish. It can draw and edit paths, handle artboards, import and export several formats, and run headlessly. Its missing list includes 3D and Materials, raster effects, fuller CJK composition and a pass over small modifier-key behaviors. Packaging for Windows and Linux was still listed as missing in the status text even though release assets appeared later, a sign of how quickly documentation can trail this release cadence.
EffectCraft draws the clearest line. Its readiness section says the app is not ready to replace After Effects for client work. It cannot open .aep or .aepx projects, cannot run After Effects plug-ins and lacks automated render comparisons with Adobe's output. Linux and Windows users have reported basic interaction bugs. A list of 306 effects is impressive as inventory, but the repository does not yet measure how closely each one behaves.
Clean-room rules are part of the engineering claim
Each project calls itself a clean-room reimplementation. In practice, the repositories turn that phrase into contribution rules: work from public specifications and observed behavior, do not inspect Adobe binaries, do not copy Adobe assets, and avoid borrowing GPL photo or raw-processing code. LightCraft's contribution section requires asset attribution in the same commit and bars panic-style error handling in shipped code. EffectCraft says its contributors use public After Effects documentation and behavioral observation.
The source code is generally offered under MIT or Apache 2.0 terms, while ArtCraft names and logos remain separately controlled trademarks. Those rules are public and checkable in future contributions, though the clean-room history itself has not been independently audited in the material reviewed for this article. Anyone planning to redistribute a fork should read the repository's notices and brand license instead of assuming the code license covers every bundled name or asset.
Stars cannot grade colour, typography or timing
A photographer switching editors will care about camera-specific colour and raw decoding before repository popularity. A PDF editor has to preserve odd fonts, forms and signatures. An illustration tool must round-trip paths and text without small shifts, while a compositor has to reproduce timing and pixels across a full render. The projects' own readiness notes acknowledge those tests unevenly and often describe their figures as self-assessments.
The next useful numbers will move more slowly than the star counter. Watch for outside compatibility suites, fixed sample files attached to bug reports, stable project formats and independent comparisons against the Adobe workflows each app names. Also watch whether contributors can extend the shared command model without creating separate behavior for the interface and the agent. If that invariant holds while the disclosed file-format gaps close, the first-week attention will have pointed to durable software rather than four unusually busy repository pages.