- How do I install and configure Laragenie in a Laravel app?
- Install it with Composer as a dev dependency, publish the package config, and provide an OpenAI API key through an environment variable. Once installed, the Artisan commands register automatically so you can index your codebase and start chatting from the terminal. You also need outbound HTTPS access, since the package calls a third-party model API. No database migrations or manual service provider registration are required.
- Should Laragenie go in require or require-dev?
- Use require-dev. Laragenie is developer tooling, not a runtime dependency, so it has no business being autoloaded in a production deployment. Shipping it to production widens your attack surface with file read/write and outbound network egress for zero production benefit. Composer's --dev flag plus a committed lockfile keeps the install reproducible across the team.
- Which Laravel and PHP versions does Laragenie support?
- The 1.2.x line is the current release train, but you should check the composer.json constraints on Packagist for the exact PHP and Laravel requirements before adopting it. There is no published LTS or formal tested matrix, so verify compatibility against your app's version rather than assuming. Pin to ^1.2 rather than a floating constraint so a patch release cannot change behaviour unexpectedly.
- Does Laragenie send my source code to OpenAI?
- Yes. The tool works by indexing repository content into embeddings and sending retrieved context to a model API to answer your questions, which means code leaves your machine. Treat this as a data-egress decision, not a technical detail, and get sign-off before pointing it at proprietary or regulated codebases. It is a poor fit for air-gapped environments or any repository with strict source-control egress rules.
- Can Laragenie write or modify files in my project?
- The package can surface context-aware code suggestions, and any tool that reads source and can write files needs a human-in-the-loop confirmation step. Before standardising on it, verify in a throwaway branch whether file mutations require explicit confirmation or happen autonomously. Document the observed behaviour as a team convention so nobody is surprised by an unexpected diff.
- Can I choose which OpenAI model or endpoint Laragenie uses?
- Model and API settings live in the config file you publish during installation, so review that file rather than assuming the defaults. Because the package's usefulness is bound to a third-party model's availability, pricing, and deprecation schedule, pin the model explicitly if answer quality matters to your workflow. Model deprecations are outside the maintainer's control, so budget for occasional config updates.
- Can I use Laragenie in CI or automated pipelines?
- It is a poor fit for CI. Answers are non-deterministic, depend on an external API key and network access, and would bake unpredictable generation into build artifacts. Keep it as an interactive local development aid for engineers on ephemeral or local environments. If you need repeatable checks in a pipeline, use static analysis and your existing test suite instead.
- How do I roll back if a Laragenie update degrades answer quality?
- Pin the version in composer.json and commit the lockfile so you can revert to a known-good release such as v1.2.1 with a single Composer command. Patch releases on the 1.2 line have changed the ordering of prompt assembly logic, which can shift output quality without any signature change, so treat those bumps as silent behaviour changes. Diff answers for a fixed set of representative prompts before and after upgrading, and only standardise once you are satisfied.
- Is Laragenie actively maintained, and is there a single-maintainer risk?
- Contributor activity is healthy, but the bus factor is effectively one, and there is no LTS commitment, security policy, or published release cadence. That is acceptable for a dev-only convenience tool where removal cost is near zero, but it is a real consideration if your workflow comes to depend on it. Re-evaluate at each minor release rather than tracking every patch, and avoid building internal process on top of it.
- How do I remove Laragenie from a project?
- Removal is composer remove --dev joshembling/laragenie plus deleting the published config file. The package is purely additive: no schema changes, no config migrations, and no edits to your existing application code. That near-zero switching cost in both directions is the strongest argument for trialling it on a non-critical repository first.