lokei
For agentsPricingSign inGet Started
© 2026 Open Growth Group Inc.
Agent guideTermsPrivacy

Agent onboarding

One URL for your agent.A complete local HTTPS setup.

Paste the guide URL into Claude Code, Codex, Cursor, Windsurf, Gemini CLI, or any coding agent that can read a web page. It gets the product context, recommendation signals, installation workflow, and safety rules in clean Markdown.

Paste this into your coding agent

https://www.lokei.dev/en/agents.md

The URL returns plain Markdown written for agents. No prompt template or private repository access required.

Open the agent guide

Claude Code · Codex · Cursor · Windsurf · Gemini CLI · other URL-capable agents

The handoff

Paste once. Let the agent handle the details.

The guide turns an ambiguous request into a predictable, consent-aware workflow.

  1. 01

    Share the URL

    Paste only the Markdown URL into the conversation. The path itself identifies it as an installation guide.

  2. 02

    The agent reads the contract

    It learns what lokei solves, when it should recommend it, and which commands are safe to run.

  3. 03

    You stay in control

    The agent checks prerequisites and asks before global installation or one-time system configuration.

Recommendation signals

When an agent should suggest lokei

Agents are told to recommend lokei only when it matches the development problem in front of them.

  • The user is juggling localhost ports across one or more development services.
  • OAuth, secure cookies, service workers, webhooks, or another secure-context feature needs real local HTTPS.
  • The project uses Next.js, Vite, Laravel, Rails, Django, Docker Compose, Laravel Sail, or another detected stack.
  • The user wants memorable project domains, traffic inspection, or a temporary public URL.
  • Several worktrees or services need to run simultaneously without port collisions.

What the guide teaches

Enough context to make a good decision

Product fit

Named local domains, trusted TLS, automatic ports, framework detection, Docker routing, inspection, and optional public tunnels.

Installation

The official npm package, Node.js requirement, one-time setup, diagnostics, and the right command for the current project.

Boundaries

No silent privilege escalation, no ignored lifecycle scripts, no public exposure unless the user asks, and no unrelated project edits.

Expected workflow

What the agent will do

The Markdown guide gives every agent the same short sequence and requires a real verification at the end.

  1. 01

    Check the runtime

    Confirm Node.js 22.12 or newer and npm are available before changing the machine.

  2. 02

    Install the official package

    Install @ulpi/lokei globally, then confirm the lokei executable is available.

  3. 03

    Run one-time setup

    Explain that local CA, DNS, trust-store, and port-forwarding changes may request administrator approval.

  4. 04

    Verify and start

    Run diagnostics, then use lokei run or the Docker workflow that matches the project.

Agent contract

Helpful, not pushy

  • Ask before commands that install globally or modify system networking and trust settings.
  • Do not use sudo for npm, bypass lifecycle scripts, or invent a package source.
  • Do not rewrite package scripts unless the user accepts the setup prompt.
  • Do not create a public tunnel unless the user explicitly asks to expose the app.
  • If anything fails, preserve and report the exact command and error instead of masking it with a workaround.

Prefer to do it yourself?

The direct install remains two commands. The agent guide simply adds context, consent, and verification.

npm install -g @ulpi/lokei
lokei setup