There's a line Goldblum delivers in Jurassic Park, somewhere between the chaos-theory monologue and the part where the lawyer gets eaten, about being so preoccupied with whether you could that nobody stopped to ask whether you should. I think about it a lot in agentic dev, because the honest answer most of the time is: we could, we did think about whether we should, and the answer was a resounding yes — let's make a coding agent you can summon from literally anywhere and have it talk like a man narrating his own documentary.
That's JEFF. The Jenerative Engine Feature Factory. The spelling crime in "Jenerative" is load-bearing — you don't get the backronym, and you don't get to have it deliver your build results in the cadence of Jeff Goldblum, without it. Worth it. Non-negotiable.
Here's the actual problem JEFF exists to kill, because under the Goldblum voice there's a genuinely annoying truth: engineering work is born in one place and done in another, and the carry between them is pure friction.
Think about where the trigger for a piece of work actually shows up. A ticket in Jira. A request — or a 2am incident — in Slack. A comment on a PR. A "hey can you just" in a meeting. Almost none of it is born in your IDE. But the IDE is where the agent lives, so the ritual is always the same: read the thing where it was born, mentally translate it, carry it over to the editor, re-establish all the context, then start. The work and the place you do the work are in different rooms, and you're the one walking back and forth between them all day.
JEFF removes the walk. It's a cloud-based coding squad you can invoke from any surface — Jira, Slack, Claude Code, or straight over the API — so you hand off the task where it's born and JEFF takes it from there. Comment on the ticket, JEFF picks it up. Slash command in Slack, JEFF's already on it. That's the "automation handoff" in the boring internal description: you don't go to JEFF, JEFF comes to wherever the work already is.
Which, if you've read Hide the Magician or Chat Can't Be the Answer, is the whole thesis wearing a hard hat. JEFF isn't a destination you visit. It's a capability that shows up in the tools you already live in. The surface is the point.
Under the hood it's not one heroic mega-agent — it's a squad, because the same thing that's true for Echo is true here: a small team of specialists beats one enormous prompt trying to hold everything at once. The rough shape is a coordinator that plans the work and delegates it, a scout that gathers the context, an engineer that does the building, and verifier/reviewer roles that check the result before it's handed back. (I'm describing the roster from memory here, so treat the exact division of labour as indicative rather than gospel — the principle of coordinated specialists is the durable bit.) Each agent owns one job and does it properly, then they reconcile, rather than one model doing five jobs at a B-minus.
JEFF doesn't work blind, either, and this is where the rest of the platform earns its keep. It's wired into Skynet, so when it picks up a ticket it already understands the codebase it's about to touch and the blast radius of the change — cross-repo, upstream and downstream — instead of discovering all that the hard way. And what JEFF ships, Echo reviews, against the policy Governor enforces. Stand back far enough and you can see the actual pipeline: Skynet gives the agents eyes, JEFF does the work, Echo reviews it, Governor keeps it inside the lines. JEFF is the factory floor; the rest is the rest of the factory.
And yes — JEFF has a Kenny Loggins mode.
If you read Kenny Loggins Mode, this is that idea made literal and given a switch. Hand JEFF a low-blast-radius task — the mechanical, reversible, nothing-burger work — flip Kenny Loggins on, and it runs unattended to completion, no babysitting, no approve-approve-approve. Hand it something gnarly and high-stakes and the prompts stay firmly on. It's the graduated, earned-trust dial from that essay, except it's a real toggle in a real product, calibrated by blast radius. The danger zone, contained, with a soundtrack.
Now, the obvious question: why the Goldblum voice? Why give a serious internal engineering tool a bit? Because — and I will die on this hill — adoption is the only metric that matters for an internal platform, and a tool nobody enjoys summoning is shelfware with good documentation. A coding squad that hands you your build results in that cadence is a tool people actually want to invoke. The personality isn't a gimmick bolted on at the end. It's an adoption strategy wearing a Hawaiian shirt. Make the powerful thing delightful to reach for and people reach for it. Make it sterile and they don't, no matter how good the engine underneath is.
So that's JEFF. Features conjured into existence and handed off — from Jira, from Slack, from wherever they were born — by a coordinated squad that sees the whole codebase, gets reviewed on the way out, and narrates the whole thing like it's mildly, delightedly astonished any of it works at all.
Life, uh, finds a way. So, it turns out, do features.