아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
최근 완료된 8시간 회차 사이 GitHub 스타 증가량 순
루팅된 LG webOS TV용 대시보드·프라이버시 제어·Home Assistant 연동
무료 오픈소스 1:1 대안, Grok Bot과 Muse 대신
AI 에이전트를 만들고 클라우드에서 실행합니다
자신의 API 키로 터미널 코딩 에이전트를 사용해 단계별 작업을 검증·재시작 가능하게 실행합니다 무료
Qwen3.5‑4B 전용 조향형 뉴런 탐색기, 모든 MLP 뉴런을 밀어 결과를 보관·탐색
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Give agents access to virtual hardware.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Simulate & validate firmware on virtual instances of real chips, straight from your AI coding agent — no hardware.
Chiplab is a hosted MCP service. Your AI coding agent connects to it, uploads compiled firmware, runs it on a virtual instance of a real microcontroller, and reads back the UART output. You don't drive the toolchain — your agent does.
We're building the next way to develop chips, in the open and early.
Today it runs Hello world! on STM32 and Nordic boards; a lot more is on the way — see veecle.ai.
Try it, poke at it, and tell us what you'd like to see.
Create a free account at veecle.ai (no credit card).
Connect your agent to the Chiplab MCP server.
git clone https://github.com/veecle/chiplab && cd chiplab, then tell your agent:
"Set up Chiplab and run the stm32f4-discovery example on it."
Your agent reads AGENTS.md, installs what it needs, builds the firmware, uploads it, runs it on the virtual board, and reports Hello world! back from the chip's UART.
That's the whole loop.
Chiplab is an HTTP MCP server at https://chiplab.veecle.ai/mcp.
Most clients take the standard mcpServers schema:
{
"mcpServers": {
"chiplab": {
"type": "http",
"url": "https://chiplab.veecle.ai/mcp"
}
}
}
On first use your client opens a browser to sign in. To verify, ask your agent to call Chiplab's discovery/help tool with no arguments.
If you cloned this repo, the server is already configured via .mcp.json — Claude Code will prompt you to trust it.
Otherwise:
claude mcp add --transport http chiplab https://chiplab.veecle.ai/mcp
Use the mcpServers block above in claude_desktop_config.json or .cursor/mcp.json.
Same block in .vscode/mcp.json, but under a servers key instead of mcpServers.
TOML in ~/.codex/config.toml:
[mcp_servers.chiplab]
url = "https://chiplab.veecle.ai/mcp"
Then sign in with codex mcp login chiplab.
The contract is framework-agnostic: your agent builds an ELF → uploads it → runs it on the target board → reads the captured UART output. Runs return synchronously and are bounded to a fixed amount of virtual time.
This repo ships a ready-to-run example for every supported board, grouped by framework — bare-metal (Rust, vendor HAL), embassy-rust (Embassy async), zephyr-os (Zephyr RTOS, C), freertos (FreeRTOS, C), and threadx (Eclipse ThreadX, C).
The full board × framework matrix is in supported-boards.md.
Toolchain and build details live in each framework's directory (examples/<framework>/README.md for humans, AGENTS.md for agents) — your agent finds them on its own.
Prefer building by hand?
Each framework README has the exact commands.
To run your own firmware, build an ELF for a supported board and ask your agent to upload and run it the same way.
Adding a board example is the easiest way in: mirror an existing example for the same framework and add a row to supported-boards.md.
All conventions live in AGENTS.md and each framework's AGENTS.md.
New chip, OS, or peripheral support is server-side — open a request instead of adding an example for an unsupported board.
This is Chiplab's public home — bugs, feature ideas, and chip/OS/peripheral requests all belong in this repo's issues. Requests really do shape the roadmap — see veecle.ai/roadmap for what's planned, or come say hi on Discord.
MIT © 2026 Veecle GmbH.