What Not to Plant Together: The Real Antagonists

Antagonist warnings are everywhere in companion-planting folklore, and most of them don't survive close inspection - a lot of "keep these apart" advice turns out to be a guess repeated so many times it started sounding like a fact. This isn't a list of every antagonist pairing we track. It's a shorter, more useful one: the handful of cases where the reasoning is real, explainable, and worth actually planning around.

Fennel: The Rare Case of Real Allelopathy

Allelopathy - one plant chemically suppressing another's growth through compounds it releases into the soil - gets invoked constantly in casual gardening advice and confirmed almost never. Fennel is the exception. Its roots and foliage release anethole-family compounds that measurably inhibit growth in a range of neighboring plants, an effect that shows up consistently enough in agricultural research to be treated as settled rather than speculative. Practically, that means fennel doesn't belong interplanted through a mixed vegetable bed at all - it wants a dedicated bed or a large container of its own, several feet from anything it might affect, nightshades especially. We cover the specific mechanics of this for tomatoes, peppers, potatoes, and eggplant individually, since the practical fix looks slightly different depending on whether the neighboring crop's edible part hangs above ground or develops as a tuber underground.

Nightshades Sharing a Disease, Not Just a Family

Potatoes and tomatoes being kept apart isn't about competing for nutrients or space - the two nightshades share a specific pair of fungal-like pathogens responsible for early and late blight, and standing close together simply shortens the trip an outbreak has to make from one crop to the other. That's real plant pathology, not the looser "same family, keep them apart" instinct applied elsewhere in garden folklore. Bed history matters here more than a spacing rule: a plot where blight has shown up before deserves distance for both crops from that spot in future seasons, not just distance from each other this year.

A Pathogen That Ignores Plant Families Entirely

Verticillium wilt breaks the usual pattern entirely. Where a normal shared-disease antagonist involves two related crops vulnerable to the same specialized threat, this fungus doesn't care about family lines at all - it happily infects nightshades and cucurbits alike, two groups with nothing in common botanically. That's the reason cucumbers get flagged as a caution near both potatoes and tomatoes on this site: not shared ancestry, just shared bad luck at being susceptible to the same generalist. And because the fungus survives in soil on its own, without needing a living host to hang on, a single clean season of rotation often isn't enough to clear a bed that's had it before - once it's established, plan on several years of caution with susceptible crops, not one.

Alliums and Legumes: A Documented Chemical Conflict

This is the one entry on this page that runs against the grain of most allium advice elsewhere on the site, where onions and garlic are usually the helpful neighbor rather than the problem. Legumes are the exception. Research into how alliums and legumes interact has found onions and garlic doing something more specific than a generic scent effect - their sulfur chemistry interferes with the nodulation process legume roots depend on to fix nitrogen in the first place, measurably setting back bean and pea growth in the process. That's settled enough to plan around rather than shrug off, which is why a rotation sequence should never put a legume directly into a bed an allium just vacated - give it a full season's gap at minimum.

Same-Family Root Crops: Usually a Missed Opportunity, Not a Real Threat

Not every antagonist listing on this page rises to the level of a genuine hazard, and it's worth being honest about the milder end of the scale too. Carrots and parsnips are both in the carrot family, which means growing them together doesn't confuse the pests that target either one the way a genuinely different-family neighbor like onion can - it just puts two hosts of the same pest, and two taproots competing for the same soil layer, in the same bed. That's a missed opportunity rather than a real conflict: nothing dramatic goes wrong, you simply don't get the complementary benefit a better-matched pairing would offer.

What We Deliberately Left Off This List

Plenty of antagonist claims circulate that we don't include here, because the reasoning behind them doesn't hold up to the same scrutiny as the pairings above. Vague warnings about "competing energies" or unnamed chemical interactions with no described mechanism, claims that contradict each other depending on which chart you're reading, and pairings justified only by "gardeners have always said so" - we track those too, individually, and rate them honestly as traditional lore or note when we think a listed antagonist relationship is actually thin. This page is specifically the short list where we're confident enough in the underlying reasoning to call it a real conflict worth planning your garden around, not a catalogue of everything that's ever been called an antagonist somewhere.

Planning Around Real Antagonists

The practical response differs by mechanism. Allelopathy problems like fennel's need physical distance and often a dedicated bed - proximity is the whole issue. Shared-disease-risk problems like nightshade blight and Verticillium are as much about rotation history as current-season spacing, since both pathogens can persist in soil or return from infected debris. Chemical suppression between alliums and legumes is really a rotation-planning question, best solved by keeping the two apart across seasons rather than trying to manage a safe distance within one bed. None of these require abandoning a small garden's layout entirely - they mostly require knowing which few pairings actually warrant that kind of planning, instead of treating every antagonist warning you encounter as equally serious.