lopebase 0.0.0-stage → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +94 -2
  2. package/dist/lopebase.js +1883 -0
  3. package/package.json +57 -4
package/README.md CHANGED
@@ -1,3 +1,95 @@
1
- # Temporary Holding Version
1
+ <p align="center">
2
+ <a href="https://lopebase.com"><img src="https://lopebase.com/icon-512.png" width="72" height="72" alt="LopeBase"></a>
3
+ </p>
2
4
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
5
+ <h1 align="center">lopebase</h1>
6
+
7
+ <p align="center">
8
+ Set up <a href="https://lopebase.com">LopeBase</a> from your project's own folder.<br>
9
+ Your coding agent does the steps. It stops for you only when it has to.
10
+ </p>
11
+
12
+ <p align="center">
13
+ <a href="https://lopebase.com">Website</a> ·
14
+ <a href="https://lopebase.com/agents">For agents</a> ·
15
+ <a href="https://lopebase.com/pricing">Pricing</a> ·
16
+ <a href="https://www.npmjs.com/package/@lopebase/adapter">@lopebase/adapter</a>
17
+ </p>
18
+
19
+ ---
20
+
21
+ LopeBase is one place to see and run all of your products: traffic, search,
22
+ signups, revenue, and errors side by side, with a weekly summary and an agent
23
+ that can help. This CLI connects a project to it in a few minutes.
24
+
25
+ ## Quick start
26
+
27
+ In the folder of any project you run:
28
+
29
+ ```sh
30
+ npx lopebase
31
+ ```
32
+
33
+ 1. **Scan.** It reads your `package.json` files, config file names, and the
34
+ variable *names* in example env files, then shows your stack, the services
35
+ you already use, and what is missing (for example analytics or error
36
+ tracking).
37
+ 2. **Connect this computer.** It opens your LopeBase workspace and shows a
38
+ short code. Check it matches and press Connect.
39
+ 3. **Pick what to connect.** Services already in your code are ticked; the
40
+ ones you do not use yet are offered, never forced.
41
+ 4. **Hand over to your agent.** It finds the coding agents you have installed
42
+ (Claude Code, Codex, Gemini CLI, opencode, Cursor Agent), gives the one you
43
+ choose the LopeBase tools, and starts it with what the scan found. The agent
44
+ does the setup and asks you when it needs a sign-in, a key, or a decision.
45
+
46
+ No agent installed? It prints the prompt for you to paste instead.
47
+
48
+ ## Commands
49
+
50
+ | Command | What it does |
51
+ | --- | --- |
52
+ | `npx lopebase` | Scan, connect, choose, and hand over to your agent. |
53
+ | `npx lopebase login` | Connect this computer to your workspace with a short code. `--paste` to paste an agent token instead. |
54
+ | `npx lopebase scan` | Show what the scan found. `--json` for scripts. |
55
+ | `npx lopebase prompt` | Print the setup prompt instead of starting an agent. |
56
+ | `npx lopebase mcp` | Run the LopeBase tools as a local MCP server (stdio) for any agent. |
57
+ | `npx lopebase adapter secret` | Print a new signing secret for [@lopebase/adapter](https://www.npmjs.com/package/@lopebase/adapter). Pipe it straight into your secret store. |
58
+ | `npx lopebase adapter check <url>` | Test a running adapter, local or deployed, before you connect it. |
59
+
60
+ ## What it reads, and what it keeps
61
+
62
+ - **Reads:** `package.json` files at the root and in `apps/`, `packages/`,
63
+ and similar folders; config file names such as `wrangler.toml` or
64
+ `vercel.json`; and the variable names in `.env.example` style files.
65
+ - **Never reads** a real `.env` file, and never sends a value anywhere. Only
66
+ names leave your machine, and only to your own workspace.
67
+ - **Keeps** one thing: an agent token in `~/.config/lopebase/auth.json`,
68
+ readable only by you. It lasts 30 days, acts as the workspace admin who
69
+ approved it, is limited to what that admin allowed, and can be revoked any
70
+ time under Settings, Agent access.
71
+ - `LOPEBASE_TOKEN` and `LOPEBASE_URL` override the saved values, for CI or
72
+ another machine.
73
+
74
+ ## Use it with any agent
75
+
76
+ `npx lopebase` sets this up for you. To add the tools by hand, register this
77
+ as a stdio MCP server in your agent:
78
+
79
+ ```sh
80
+ npx -y lopebase mcp
81
+ ```
82
+
83
+ Or point an agent that supports remote MCP straight at your workspace, for
84
+ example `https://yourteam.lopebase.com/api/mcp`. It will ask you to sign in.
85
+
86
+ ## Requirements
87
+
88
+ Node 18 or newer. Works on macOS, Linux, and Windows.
89
+
90
+ ## Help
91
+
92
+ Questions or problems: [contact@jackalope.digital](mailto:contact@jackalope.digital).
93
+ Privacy: [app.lopebase.com/legal/privacy](https://app.lopebase.com/legal/privacy).
94
+
95
+ LopeBase is made by [Jackalope Digital](https://jackalope.digital).