Red Chili, the Chip Project Brain
The right project context for every chip-design task.
Red Chili keeps a coherent, current picture of your chip project, from spec to layout, and gives the coding agent your team already uses exactly what each task needs.
- ✓ ERROR response takes two cyclesAMBA 5 AHB
- ✓ Valid / accept handshakehouse conventions
- ✓ Async active-low resetDEV.md
A brain, not memory
Memory stores notes. A brain understands the project.
Agents and platforms already keep notes, history and retrieved text. Red Chili adds what memory alone does not.
Knowledge
Knows the structure, flows and dependencies of your project: where things are and why.
Coherence
One consistent view across spec, RTL, verification and implementation.
Maintenance
Kept current as the project changes, with stale facts caught and corrected.
Accessibility
Reachable by every engineer and agent, through the tools they already use.
Focus
Only what the current task needs, so agents spend their effort on the work.
The problem
Engineers and AI agents don’t know which project facts matter for the task in front of them.
Chip-design knowledge is spread across specs, RTL, verification, tickets, tools and people. It goes stale and stays implicit.
Rediscovery
Design and verification intent is worked out again and again, by people and agents alike.
Incoherent context
Agents edit code from scattered, stale or contradictory facts, and their output shows it.
Lost intent
Intent slips between spec, RTL and verification, so a change breaks what nobody wrote down.
The problem isn’t a lack of information.
Most teams already have too much. What’s missing is coherent, task-shaped information: what does this engineer or agent need to know for this exact task, right now?
How Red Chili works
A continuously maintained, evidence-backed model of your chip that learns from every task your engineers and agents complete.
- 1
Collect
Ingest RTL, specs, tickets, plans, coverage, regressions and debug notes.
- 2
Structure
Organize it into semiconductor-aware knowledge: modules, interfaces, tests, assertions, failures.
- 3
Validate
Back every fact with evidence, scope and freshness.
- 4
Distill
Compile only what the current task needs into a focused briefing.
- 5
Deliver
Hand the briefing to the engineer or straight to their coding agent.
- 6
Learn
Confirmed facts and accepted changes flow back in.
Every finished task makes the next briefing sharper.
What focused context buys you
Better agent output
Agents work from verified facts and clear boundaries, so first attempts land closer to done.
Lower agent spend
Agents stop burning credits searching, rereading and retrying. They get the context up front and spend their budget on the task.
Faster ramp-up
Engineers start on a block with a briefing, not a week of archaeology.
Traceable by default
Every answer points to its source, from spec to regression.
Proven on our own IP
We build chips with it first
We build our own RISC-V CPUs, SoC IP and an edge AI accelerator with Red Chili and today’s coding agents.
- more CoreMark per second than Ibex maxperf
- +38%
- higher clock than Ibex maxperf
- +59%
- of verified modules, from library to SoC
- Hundreds
ChillU-S against Ibex maxperf, in the same ORFS flow on the same CoreMark binary.
Built for agent-driven chip design
As chip design becomes agent-driven, Red Chili helps the engineering infrastructure evolve with it. We’re opening pilots for RTL and DV teams already using coding agents.
Request a Pilot