Labs

Try Meko features using a live demo application in the portal

Use Labs to explore core Meko features with a live demo application connected to a real datapack. Each lab walks a stage of the agentic development lifecycle: you build the context, an agent uses it, and you see exactly what it changed. Every lab ends with a path back to your own repo. Nothing to install.

Labs sit in that lifecycle — Spec, Build, Review, Fix & merge — with Review live today.

To run a lab:

  1. Sign up.
  2. Log in.
  3. In the portal sidebar, open Labs, choose a scenario, and click Launch lab.
  4. Follow the on-screen instructions.

Labs

The following lab is available (with more in development).

Agentic coding review (ADLC)

Learn how an agent reviews a pull request against your org's coding standards, live. You start with a sample project that has no standards yet, build that context in a datapack, then watch AgentK use it.

The lab takes about five minutes across four chapters:

  1. Give your agent context. Watch AgentK review a pull request with no standards, then build the datapack it was missing: a standards document, a memory, and a conversation.
  2. Share it with AgentK. Grant the agent read access to that datapack, choose how it reads context and which model runs, and decide where it stops for a human.
  3. Review the results. Run the review, read each finding against the code it flagged and the rule behind it, write the findings back into a datapack, and see what the context cost.
  4. See it in production. Watch a batch go past unattended, then read AgentK's real reviews on Yugabyte's public repositories and the numbers behind a month of them. Optionally point it at a pull request of your own.

AgentK runs on AWS Bedrock AgentCore.

Limitations

  • Creating a datapack during a lab counts against your plan's datapack quota. Free accounts can create up to 10 datapacks. See Meko pricing.
  • Free accounts use the shared, predeployed AgentK. Deploying a dedicated instance requires a paid plan.
  • Pointing AgentK at your own pull request is optional. Your GitHub personal access token stays in the browser; Meko never receives it. The PR title and full diff are then sent to Meko and the review agent — on the Free tier, the shared predeployed instance.