Skip to main content
Get up to speed on a codebase, fix bugs, add drivers, or refactor—Seb reads your board config, MCU, peripherals, and drivers, then writes files, runs commands, and makes changes. Not just answers: it edits code, runs builds, and flashes when you ask.

​
What Seb uses from your project

  • MCU and Board — Target, clock speeds, memory layout, board settings
  • Peripherals — I2C, SPI, UART, ADC, GPIO, etc.
  • Sensor Drivers — All drivers and their interfaces
  • Hardware Constraints — Pin assignments, timing, electrical characteristics
Seb creates and maintains SEB.md in your project root with software/hardware context. You can add project-specific notes there for Seb to use.

​
What you can ask Seb to do

  • Understand — “What is my project doing?” · “List my current drivers” · “If there are issues that should be fixed, list them”
  • Change code — “Fix the I2C init in driver X” · “Add error handling to this function” · “Refactor this to use the HAL correctly”
  • Run things — “Build the project” · “Flash the board” · “Run the tests”
  • Add or integrate — “Add a driver for sensor Y” · “Wire this into the main loop” · “Integrate the new peripheral”
Tell Seb what you want done; it will edit files and run commands as needed.