Welcome

Welcome to OneMinute Logs.

Once the CLI has connected your app, start with an endpoint you care about. Review its monitoring in VS Code, then use your coding assistant to cover the rest of the project.

Still setting up? Open Quick Start

Instrument one API route with Pilot

  1. Open your project with the OML Pilot VS Code Extension installed. Select the code for one API endpoint. For example, in an Express app, highlight the entire route below.
    app.post("/orders", async (req, res) => {
      const order = await createOrder(req.body);
      res.status(201).json(order);
    });
  2. With the route selected, press ⌘M on macOS or Ctrl+M on Windows or Linux. You can also click the floating button above the handler. For this example, it reads Monitor POST /orders with OneMinute Pilot.
  3. Review the proposed diff. Accept it to apply the monitoring changes, or reject it to discard them. If the route already has sufficient monitoring, Pilot can skip it.
How Pilot reviews a route

Cover the project with Codex or Claude Code

Open your assistant at the same project root. If you enabled OML MCP during setup, it can look up recorded route coverage and OML’s instrumentation conventions. Paste this prompt to get started.

Instrument this project with OneMinute Logs. Read oml.json, find the API routes and the operations they call, and check what is already monitored. Use OML MCP if available. Add events for meaningful outcomes and failures, preserve existing behavior, and avoid duplicate logs. Show me the diff and list any routes that still need review.

How OML MCP works

See your first event

Run your app with the accepted changes and make a request that exercises the instrumented endpoint. Open your project in the OneMinute Logs dashboard and look for the event in Realtime Logs.

Found something unexpected? Let us know.