Port a project to Axelera

Already have a computer-vision project on another platform? The Port to Axelera catalog turns popular ecosystem projects into ready-to-run launch prompts for your Axelera hardware — four clicks from tile to running agent.

Port a project to Axelera, end to end

Where the catalog lives

Port to Axelera is a page in the Agent Dev dashboard — the hosted dashboard in your browser and the same surface embedded inside the desktop app. It lists popular computer-vision projects from partner ecosystems, grouped by vendor: NVIDIA, Hailo, Ultralytics, SiMa.ai, and Community. Every project ends in a launch prompt: the full task plan an agent needs to rebuild that project on Axelera hardware.

Browse the catalog

Port a project in four steps

  1. Pick a vendor tile

    Open the dashboard inside Agent Dev (or the hosted dashboard in a browser) and go to Port to Axelera. Pick the vendor tile that matches where your project lives today.

  2. Open the project detail

    Each project card opens a detail page: what the project does, what it needs, and the prepared launch prompt. Read the prompt — it is the whole plan, and you should know what the agent is about to do.

  3. Launch with Open in Agent Dev

    Press Open in Agent Dev for the one-click path. A confirmation modal shows the full prompt with Cancel and Run — nothing launches until you press Run. The prompt is also copied to your clipboard at the same time, so you can always paste it manually.

  4. Approve the first execution

    Run submits the prompt to the Agent Dev panel. The agent runs on your device through your installed, signed-in Claude Code, Codex, or Kimi CLI — approve its first execution request and watch the port take shape.

Launch a port

Copy the prompt instead

  • Four clicks, one gate: Vendor tile, project card, launch prompt, Run — the whole port flow is four clicks with a review gate in the middle.
  • Prompts are the product: The launch prompt is visible, editable text. Read it in the confirmation modal before Run; paste and adapt it when you want a variation.
  • Your device, your agent: Execution happens on your machine through your installed, signed-in provider CLI — the catalog prepares the plan, Agent Dev does the work.