leashbyte 0.1.1__tar.gz → 0.1.2__tar.gz

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 (88) hide show
  1. leashbyte-0.1.2/.github/ISSUE_TEMPLATE/bug_report.yml +70 -0
  2. leashbyte-0.1.2/.github/ISSUE_TEMPLATE/config.yml +5 -0
  3. leashbyte-0.1.2/.github/ISSUE_TEMPLATE/feature_request.yml +29 -0
  4. leashbyte-0.1.2/.github/PULL_REQUEST_TEMPLATE.md +16 -0
  5. leashbyte-0.1.2/CHANGELOG.md +50 -0
  6. {leashbyte-0.1.1 → leashbyte-0.1.2}/CONTRIBUTING.md +25 -2
  7. {leashbyte-0.1.1 → leashbyte-0.1.2}/PKG-INFO +32 -23
  8. {leashbyte-0.1.1 → leashbyte-0.1.2}/README.md +30 -21
  9. {leashbyte-0.1.1 → leashbyte-0.1.2}/SECURITY.md +1 -1
  10. {leashbyte-0.1.1 → leashbyte-0.1.2}/docs/DESIGN.md +7 -2
  11. {leashbyte-0.1.1 → leashbyte-0.1.2}/docs/ROADMAP.md +0 -2
  12. {leashbyte-0.1.1 → leashbyte-0.1.2}/docs/python-licenses.json +1 -1
  13. {leashbyte-0.1.1 → leashbyte-0.1.2}/openapi.json +11 -1
  14. {leashbyte-0.1.1 → leashbyte-0.1.2}/pyproject.toml +2 -2
  15. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/python/pyproject.toml +1 -1
  16. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/python/src/leashbyte_sdk/_models.py +2 -0
  17. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/typescript/README.md +11 -8
  18. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/typescript/package-lock.json +2 -2
  19. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/typescript/package.json +1 -1
  20. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/typescript/src/schema.ts +10 -0
  21. {leashbyte-0.1.1 → leashbyte-0.1.2}/site/package-lock.json +2 -2
  22. {leashbyte-0.1.1 → leashbyte-0.1.2}/site/package.json +1 -1
  23. {leashbyte-0.1.1 → leashbyte-0.1.2}/site/src/App.tsx +1 -1
  24. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/__init__.py +1 -1
  25. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/agent_worker.py +18 -5
  26. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/browser.py +98 -22
  27. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/config.py +10 -1
  28. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/model_adapter.py +74 -20
  29. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/models.py +2 -0
  30. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/run_models.py +14 -0
  31. {leashbyte-0.1.1 → leashbyte-0.1.2}/tests/test_agent_security.py +102 -2
  32. {leashbyte-0.1.1 → leashbyte-0.1.2}/uv.lock +2 -2
  33. leashbyte-0.1.1/CHANGELOG.md +0 -32
  34. {leashbyte-0.1.1 → leashbyte-0.1.2}/.dockerignore +0 -0
  35. {leashbyte-0.1.1 → leashbyte-0.1.2}/.env.example +0 -0
  36. {leashbyte-0.1.1 → leashbyte-0.1.2}/.github/workflows/ci.yaml +0 -0
  37. {leashbyte-0.1.1 → leashbyte-0.1.2}/.gitignore +0 -0
  38. {leashbyte-0.1.1 → leashbyte-0.1.2}/CODE_OF_CONDUCT.md +0 -0
  39. {leashbyte-0.1.1 → leashbyte-0.1.2}/Dockerfile +0 -0
  40. {leashbyte-0.1.1 → leashbyte-0.1.2}/LICENSE +0 -0
  41. {leashbyte-0.1.1 → leashbyte-0.1.2}/NOTICE +0 -0
  42. {leashbyte-0.1.1 → leashbyte-0.1.2}/ci/compose-smoke.sh +0 -0
  43. {leashbyte-0.1.1 → leashbyte-0.1.2}/ci/fill_fixture.py +0 -0
  44. {leashbyte-0.1.1 → leashbyte-0.1.2}/ci/http_fixture.py +0 -0
  45. {leashbyte-0.1.1 → leashbyte-0.1.2}/ci/mcp_roundtrip.py +0 -0
  46. {leashbyte-0.1.1 → leashbyte-0.1.2}/compose.yaml +0 -0
  47. {leashbyte-0.1.1 → leashbyte-0.1.2}/docs/THIRD_PARTY.md +0 -0
  48. {leashbyte-0.1.1 → leashbyte-0.1.2}/examples/quickstart.py +0 -0
  49. {leashbyte-0.1.1 → leashbyte-0.1.2}/scripts/generate_openapi.py +0 -0
  50. {leashbyte-0.1.1 → leashbyte-0.1.2}/scripts/python_licenses.py +0 -0
  51. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/python/LICENSE +0 -0
  52. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/python/NOTICE +0 -0
  53. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/python/README.md +0 -0
  54. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/python/src/leashbyte_sdk/__init__.py +0 -0
  55. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/python/src/leashbyte_sdk/client.py +0 -0
  56. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/typescript/LICENSE +0 -0
  57. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/typescript/NOTICE +0 -0
  58. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/typescript/THIRD_PARTY_LICENSES.json +0 -0
  59. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/typescript/scripts/licenses.mjs +0 -0
  60. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/typescript/src/index.ts +0 -0
  61. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/typescript/test/redaction.test.ts +0 -0
  62. {leashbyte-0.1.1 → leashbyte-0.1.2}/sdk/typescript/tsconfig.json +0 -0
  63. {leashbyte-0.1.1 → leashbyte-0.1.2}/site/README.md +0 -0
  64. {leashbyte-0.1.1 → leashbyte-0.1.2}/site/index.html +0 -0
  65. {leashbyte-0.1.1 → leashbyte-0.1.2}/site/public/favicon.svg +0 -0
  66. {leashbyte-0.1.1 → leashbyte-0.1.2}/site/src/main.tsx +0 -0
  67. {leashbyte-0.1.1 → leashbyte-0.1.2}/site/src/styles.css +0 -0
  68. {leashbyte-0.1.1 → leashbyte-0.1.2}/site/tsconfig.json +0 -0
  69. {leashbyte-0.1.1 → leashbyte-0.1.2}/site/vite.config.ts +0 -0
  70. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/browser_service.py +0 -0
  71. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/errors.py +0 -0
  72. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/fetch.py +0 -0
  73. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/internal.py +0 -0
  74. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/main.py +0 -0
  75. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/mcp/__init__.py +0 -0
  76. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/mcp/server.py +0 -0
  77. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/model_relay.py +0 -0
  78. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/proxy.py +0 -0
  79. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/run_store.py +0 -0
  80. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/run_viewer.py +0 -0
  81. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/search.py +0 -0
  82. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/url_guard.py +0 -0
  83. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/vault.py +0 -0
  84. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/vault_service.py +0 -0
  85. {leashbyte-0.1.1 → leashbyte-0.1.2}/src/leashbyte/worker_service.py +0 -0
  86. {leashbyte-0.1.1 → leashbyte-0.1.2}/tests/test_browser_security.py +0 -0
  87. {leashbyte-0.1.1 → leashbyte-0.1.2}/tests/test_mcp_sdk_security.py +0 -0
  88. {leashbyte-0.1.1 → leashbyte-0.1.2}/tests/test_security.py +0 -0
@@ -0,0 +1,70 @@
1
+ name: Bug report
2
+ description: Something in LeashByte doesn't work the way the docs say it should.
3
+ labels: ["bug"]
4
+ body:
5
+ - type: markdown
6
+ attributes:
7
+ value: |
8
+ Thanks for taking the time to report this. If you think you've found a security problem, please stop here and use the [private report form](https://github.com/mangybyte/leashbyte/security/advisories/new) or email `security@leashbyte.com` instead. [SECURITY.md](https://github.com/mangybyte/leashbyte/blob/main/SECURITY.md) has the details.
9
+ - type: input
10
+ id: version
11
+ attributes:
12
+ label: Version or commit
13
+ description: The release you installed, or the commit you built from (`git rev-parse --short HEAD`).
14
+ placeholder: 0.1.1, or a commit hash
15
+ validations:
16
+ required: true
17
+ - type: textarea
18
+ id: environment
19
+ attributes:
20
+ label: How you run the stack
21
+ description: |
22
+ Tell us how LeashByte is set up. For example: the Docker and Compose versions, the host OS, whether you changed `compose.yaml` or `.env`, and which model server you use (Ollama, vLLM, llama-server, LM Studio, the Anthropic API) and its version. If you only use an SDK or `leashbyte-mcp`, say which one and its version.
23
+
24
+ Don't paste your `.env`: it holds every key the stack uses. Name the variables you changed, not their values.
25
+ placeholder: |
26
+ Docker 28.x, Compose 2.x, Ubuntu 24.04
27
+ Default compose.yaml, LEASHBYTE_LOCAL_MODEL_PORT changed to 8080
28
+ llama-server build 1234
29
+ validations:
30
+ required: true
31
+ - type: textarea
32
+ id: actual
33
+ attributes:
34
+ label: What happened
35
+ description: Include the HTTP status and error code if the API returned one.
36
+ validations:
37
+ required: true
38
+ - type: textarea
39
+ id: expected
40
+ attributes:
41
+ label: What you expected
42
+ validations:
43
+ required: true
44
+ - type: textarea
45
+ id: steps
46
+ attributes:
47
+ label: Steps to reproduce
48
+ description: The smallest set of steps that shows the problem. A request body or a short script is ideal.
49
+ placeholder: |
50
+ 1. docker compose up --build -d --wait
51
+ 2. curl -H "X-API-Key: ..." ...
52
+ 3. ...
53
+ validations:
54
+ required: true
55
+ - type: textarea
56
+ id: logs
57
+ attributes:
58
+ label: Logs
59
+ description: |
60
+ Output from `docker compose logs <service>` or the client. Before you paste anything, remove API keys, tokens, vault values, cookies and any personal data. Request dumps need a look too: your API key travels in the `X-API-Key` header, and requests between the services carry `X-Service-Key`, the CDP key and the vault keys.
61
+ render: text
62
+ validations:
63
+ required: false
64
+ - type: textarea
65
+ id: extra
66
+ attributes:
67
+ label: Anything else
68
+ description: Workarounds you found, or anything you've already ruled out.
69
+ validations:
70
+ required: false
@@ -0,0 +1,5 @@
1
+ blank_issues_enabled: true
2
+ contact_links:
3
+ - name: Report a security vulnerability
4
+ url: https://github.com/mangybyte/leashbyte/security/advisories/new
5
+ about: Please don't open a public issue for this. Use the private report form, or email security@leashbyte.com.
@@ -0,0 +1,29 @@
1
+ name: Feature request
2
+ description: Suggest a change or something new.
3
+ labels: ["enhancement"]
4
+ body:
5
+ - type: markdown
6
+ attributes:
7
+ value: |
8
+ If your idea comes from a way around one of LeashByte's protections, please send it through the [private report form](https://github.com/mangybyte/leashbyte/security/advisories/new) or to `security@leashbyte.com` instead.
9
+ - type: textarea
10
+ id: problem
11
+ attributes:
12
+ label: The problem
13
+ description: What are you trying to do, and what gets in the way today?
14
+ validations:
15
+ required: true
16
+ - type: textarea
17
+ id: idea
18
+ attributes:
19
+ label: Your idea
20
+ description: How you'd like it to work. A rough sketch of the API or config is fine.
21
+ validations:
22
+ required: true
23
+ - type: textarea
24
+ id: alternatives
25
+ attributes:
26
+ label: Other ways you looked at
27
+ description: Workarounds you've tried, or other approaches and why they fall short.
28
+ validations:
29
+ required: false
@@ -0,0 +1,16 @@
1
+ ## What changed and why
2
+
3
+ <!-- A short description of the change and the reason for it. -->
4
+
5
+ Linked issue: #
6
+
7
+ ## How you tested it
8
+
9
+ <!-- The commands you ran, and anything you checked by hand. -->
10
+
11
+ ## Checklist
12
+
13
+ - [ ] CI passes, or I've explained below why a check fails.
14
+ - [ ] I updated the docs (README, docs/, SECURITY.md) where the change needs it.
15
+ - [ ] The diff contains no keys, tokens, credentials or personal data, including in tests and fixtures.
16
+ - [ ] I understand every line of this change and I have tested it myself.
@@ -0,0 +1,50 @@
1
+ # Changelog
2
+
3
+ ## 0.1.2 - 2026-11-10
4
+
5
+ Agents can now read the page they are on.
6
+
7
+ ### Added
8
+
9
+ - Snapshots and agent observations carry the rendered text of the page in reading order, as `text`, cut at 4,000 characters, with `text_truncated` set when we cut it. Secret values are redacted from it the same way as element names. Before, the model only saw the title and the names of links, buttons and form fields, so it could not answer a question about a paragraph or a price.
10
+
11
+ ### Changed
12
+
13
+ - The agent prompt tells the model to answer only from the observation and to fail when the answer isn't there, rather than guess.
14
+ - The schema we send to Claude now states the numeric and length limits in the field descriptions, since the API doesn't accept them as constraints. Waits and scroll offsets outside their limits are clamped instead of failing the run.
15
+ - When a model reply fails validation, the run error now says which check failed (for example `string_too_long at result`), without any of the reply text.
16
+ - An Anthropic key file that the worker can't read now gives a clear run error and a warning at start. The README explains the access the file needs.
17
+ - Element names are redacted before they are cut, so a secret can't show up in part at the cut.
18
+ - README links point at the release tag, so the PyPI page doesn't change under you.
19
+
20
+ ## 0.1.1 - 2026-11-10
21
+
22
+ The first release on PyPI, as `leashbyte` and `leashbyte-sdk`. 0.1.0 was a GitHub-only release and was never uploaded to a package registry. There are no code changes.
23
+
24
+ ### Changed
25
+
26
+ - The READMEs and the project site now give the PyPI install lines.
27
+ - `leashbyte` now requires `leashbyte-sdk>=0.1.1,<0.2`. Before, it accepted any version.
28
+ - The TypeScript SDK is on npm as `leashbyte` 0.1.1. Its code is the same as the `v0.1.1` tag. We published it from a later commit that only changes the docs, so the README in the package gives the npm install line.
29
+
30
+ ## 0.1.0 - 2026-11-10
31
+
32
+ First public source release.
33
+
34
+ ### Added
35
+
36
+ - Web search through a separate SearXNG service.
37
+ - Page fetch with Markdown, cleaned HTML and parsed JSON output, with time, size and redirect limits.
38
+ - Destination checks on fetch and browser traffic, so neither can reach internal addresses by default.
39
+ - Isolated Chrome sessions with named profiles, page actions and short-lived CDP access.
40
+ - An encrypted credential vault that only fills a credential on the exact origins it's granted to.
41
+ - Goal-driven agent runs with limits, cancellation, run records and artifacts.
42
+ - A local run viewer.
43
+ - An MCP server with stable search, fetch, browser and run tools.
44
+ - Python and TypeScript SDKs.
45
+ - A Docker Compose stack for local use, and a static project site.
46
+ - API key authentication, a security policy and Apache-2.0 licensing.
47
+
48
+ ### Notes
49
+
50
+ LeashByte is pre-alpha. Install it from GitHub and run it with Docker Compose. The PyPI and npm packages aren't published yet and the project site isn't deployed. [Known limits and next steps](docs/ROADMAP.md) lists what's still open.
@@ -2,6 +2,8 @@
2
2
 
3
3
  LeashByte is pre-alpha and the API and security boundaries are still settling, so please open an issue before you start on anything substantial. It saves you writing a change that clashes with something already planned.
4
4
 
5
+ To report a bug or suggest a feature, [open an issue](https://github.com/mangybyte/leashbyte/issues/new/choose) and pick the matching form. When you open a pull request, the description starts from a short checklist. Fill it in rather than deleting it: it answers the questions a reviewer would ask first.
6
+
5
7
  ## Running the checks
6
8
 
7
9
  You'll need Docker with the Compose plugin, Python 3.13 with uv 0.13.4, and Node 20 or later (22.12 or later if you build the site). From the repository root:
@@ -27,7 +29,28 @@ CI runs the same checks on every push to `main` and every pull request, builds t
27
29
  - It fits the architecture in [docs/DESIGN.md](docs/DESIGN.md). If you think the design should change, say so in the issue first.
28
30
  - It contains no credentials, private data, internal host names or internal paths, not even in test fixtures.
29
31
 
30
- A maintainer reviews every pull request. Security-sensitive changes, and especially anything touching server-side fetch, browser access or the vault, get an extra security review.
32
+ ## How review works
33
+
34
+ A maintainer reads every pull request, and we don't merge one until CI passes on it.
35
+
36
+ Small, focused changes get reviewed faster. A pull request that mixes a fix with a refactor or a new feature usually goes back to be split.
37
+
38
+ Some parts of the code are where a mistake turns into a security hole, so a change to any of them gets a deeper review and takes longer:
39
+
40
+ - the vault (`vault.py`, `vault_service.py`), which holds secrets the model must never see
41
+ - browser isolation and CDP access (`browser.py`, `browser_service.py`)
42
+ - the fetch guard that keeps fetch and browser traffic away from loopback, private and metadata addresses (`url_guard.py`, `fetch.py`, `proxy.py`)
43
+ - authentication: the API key checks in the REST API and the MCP server, the separate CDP capability key, and the service keys between internal services (`main.py`, `internal.py`, `mcp/server.py`)
44
+
45
+ On a pull request from outside the project, CI doesn't start until a maintainer has read the change and approved the run. That applies to every outside pull request, so it's not a judgment on yours.
46
+
47
+ We can't promise a review date. If a change doesn't fit the project, we'll close the pull request and say why, so you're not left waiting.
48
+
49
+ ## Using AI tools
50
+
51
+ You're welcome to use AI coding tools. The bar is the same as for any other change: you understand everything you send, you've run it and tested it yourself, and you can answer questions about it in review. You're responsible for the change, whatever wrote the first draft.
52
+
53
+ A pull request that looks generated and untested, for example code that doesn't run, tests that don't test the change, or a description that doesn't match the diff, will be closed.
31
54
 
32
55
  ## New dependencies
33
56
 
@@ -35,7 +58,7 @@ LeashByte is Apache-2.0, and we want anyone to be able to use, modify and redist
35
58
 
36
59
  ## Reporting a vulnerability
37
60
 
38
- Please don't use a public issue or pull request for this. Email `security@leashbyte.com`. [SECURITY.md](SECURITY.md) has the details.
61
+ Please don't use a public issue or pull request for this. Use the [private report form](https://github.com/mangybyte/leashbyte/security/advisories/new) or email `security@leashbyte.com`. [SECURITY.md](SECURITY.md) has the details.
39
62
 
40
63
  ## Licence and conduct
41
64
 
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.5
2
2
  Name: leashbyte
3
- Version: 0.1.1
3
+ Version: 0.1.2
4
4
  Summary: Self-hosted search and page fetch APIs
5
5
  Project-URL: Homepage, https://leashbyte.com
6
6
  Project-URL: Repository, https://github.com/mangybyte/leashbyte
@@ -17,7 +17,7 @@ Requires-Dist: cryptography<51,>=50
17
17
  Requires-Dist: fastapi<1,>=0.121
18
18
  Requires-Dist: httpcore<1.1,>=1.0.9
19
19
  Requires-Dist: httpx<1,>=0.28
20
- Requires-Dist: leashbyte-sdk<0.2,>=0.1.1
20
+ Requires-Dist: leashbyte-sdk<0.2,>=0.1.2
21
21
  Requires-Dist: mcp<2,>=1.26
22
22
  Requires-Dist: playwright<2,>=1.56
23
23
  Requires-Dist: pydantic-settings<3,>=2.11
@@ -30,7 +30,7 @@ Description-Content-Type: text/markdown
30
30
 
31
31
  LeashByte is a self-hosted toolkit that gives AI agents access to the web. It puts search, page fetching, real Chrome sessions, an encrypted credential vault and goal-driven agent runs behind one REST API, with an MCP server and Python and TypeScript SDKs on top. It's meant for developers who want their agents to search, read and use websites from their own machines, driven by a model they choose. A local model works fine.
32
32
 
33
- LeashByte is pre-alpha, so expect rough edges and breaking changes. The services run with Docker Compose from a source checkout. The Python SDK is on PyPI as `leashbyte-sdk`, and the server package as `leashbyte`.
33
+ LeashByte is pre-alpha, so expect rough edges and breaking changes. The services run with Docker Compose from a source checkout. The Python SDK is on PyPI as `leashbyte-sdk`, and the server package as `leashbyte`. The TypeScript SDK is on npm as `leashbyte`.
34
34
 
35
35
  The project home is [leashbyte.com](https://leashbyte.com).
36
36
 
@@ -155,28 +155,27 @@ with LeashByteClient() as client:
155
155
 
156
156
  The client reads `LEASHBYTE_API_KEY` or `LEASHBYTE_API_KEY_FILE`. It doesn't read `LEASHBYTE_API_URL`, so pass `base_url` if the API isn't at the default `http://127.0.0.1:8080`.
157
157
 
158
- The client keeps its configured key out of `repr` and API errors. It can't do the same for your own logging, so keep request bodies, screenshots, page content and run artifacts out of your logs. There's a run example in [`sdk/python/README.md`](https://github.com/mangybyte/leashbyte/blob/main/sdk/python/README.md).
158
+ The client keeps its configured key out of `repr` and API errors. It can't do the same for your own logging, so keep request bodies, screenshots, page content and run artifacts out of your logs. There's a run example in [`sdk/python/README.md`](https://github.com/mangybyte/leashbyte/blob/v0.1.2/sdk/python/README.md).
159
159
 
160
160
  ## TypeScript SDK
161
161
 
162
- The TypeScript SDK lives in `sdk/typescript`. Its [README](https://github.com/mangybyte/leashbyte/blob/main/sdk/typescript/README.md) has the install and usage details. To build it from the checkout:
162
+ The TypeScript SDK is on npm. It has no runtime npm dependencies and uses Node's built-in `fetch` API.
163
163
 
164
164
  ```bash
165
- npm ci --prefix sdk/typescript
166
- npm --prefix sdk/typescript run build
165
+ npm install leashbyte
167
166
  ```
168
167
 
169
- Then import `LeashByteClient` from `sdk/typescript/dist/src/index.js`. It has no runtime npm dependencies and uses Node's built-in `fetch` API.
170
-
171
168
  ```typescript
172
- import { LeashByteClient } from "./sdk/typescript/dist/src/index.js";
169
+ import { LeashByteClient } from "leashbyte";
173
170
 
174
171
  const client = new LeashByteClient();
175
172
  const page = await client.fetchPage({ url: "https://example.com/" });
176
173
  console.log(page.status, page.final_url);
177
174
  ```
178
175
 
179
- It reads `LEASHBYTE_API_KEY` or `LEASHBYTE_API_KEY_FILE`. Pass `baseUrl` to the constructor for a different API address. The configured key is redacted from inspection, JSON serialization and API errors.
176
+ The source lives in `sdk/typescript`. Its [README](https://github.com/mangybyte/leashbyte/blob/v0.1.2/sdk/typescript/README.md) has more usage details and shows how to build it from the checkout.
177
+
178
+ The client reads `LEASHBYTE_API_KEY` or `LEASHBYTE_API_KEY_FILE`. Pass `baseUrl` to the constructor for a different API address. The configured key is redacted from inspection, JSON serialization and API errors.
180
179
 
181
180
  ## Using the API
182
181
 
@@ -310,7 +309,17 @@ sudo ufw allow from 172.29.250.0/24 to 172.29.250.1 port 11434 proto tcp comment
310
309
 
311
310
  Change the port in the rule if you've changed `LEASHBYTE_LOCAL_MODEL_PORT`. The rule doesn't change the model's own listener, and other networks still can't reach the relay.
312
311
 
313
- Claude runs use `claude-haiku-5-5` through the official Anthropic SDK. Put an API key in a file outside the repository and point `LEASHBYTE_ANTHROPIC_API_KEY_HOST_FILE` at it, and Compose mounts it.
312
+ Claude runs use `claude-haiku-5-5` through the official Anthropic SDK. Put an API key in a file outside the repository and point `LEASHBYTE_ANTHROPIC_API_KEY_HOST_FILE` at it, and Compose mounts it read-only at `/run/anthropic.key` in the agent worker.
313
+
314
+ The worker runs as uid 10001 with every Linux capability dropped, and a bind mount keeps the host file's owner and mode. So a key file with mode `0600` that belongs to your own user can't be read inside the container. Give uid 10001 read access and keep everyone else out. On Linux, an ACL entry does that without changing the owner:
315
+
316
+ ```bash
317
+ KEY_FILE=/path/to/anthropic.key
318
+ chmod 600 "$KEY_FILE"
319
+ setfacl -m u:10001:r--,g::--- "$KEY_FILE"
320
+ ```
321
+
322
+ A later `chmod` that gives the group nothing also resets the ACL mask and takes the read entry away again, so run `setfacl` after it. With rootless Docker or Podman, uid 10001 in the container maps to a different uid on the host, so give that uid access instead. If you don't have `setfacl`, `sudo chown 10001 "$KEY_FILE"` with mode `0400` works too. When the worker can't read the key, it logs `Claude runs are unavailable` at start, and every Claude run fails with an error that names `LEASHBYTE_ANTHROPIC_API_KEY_FILE` and the reason, such as `Permission denied`.
314
323
 
315
324
  Create a run with fixed limits:
316
325
 
@@ -400,9 +409,9 @@ The hook runs after the URL, network, robots and rate-limit checks. It receives
400
409
 
401
410
  ## Configuration
402
411
 
403
- [`.env.example`](https://github.com/mangybyte/leashbyte/blob/main/.env.example) has the main settings. Every application secret also has a `_FILE` variant for container secrets. The API won't start without an API key, and the vault won't start without a 32-byte master key.
412
+ [`.env.example`](https://github.com/mangybyte/leashbyte/blob/v0.1.2/.env.example) has the main settings. Every application secret also has a `_FILE` variant for container secrets. The API won't start without an API key, and the vault won't start without a 32-byte master key.
404
413
 
405
- The OpenAPI schema is in [`openapi.json`](https://github.com/mangybyte/leashbyte/blob/main/openapi.json).
414
+ The OpenAPI schema is in [`openapi.json`](https://github.com/mangybyte/leashbyte/blob/v0.1.2/openapi.json).
406
415
 
407
416
  ## Stopping the services
408
417
 
@@ -442,15 +451,15 @@ The GitHub Actions workflow runs the same checks. It also starts the Compose sta
442
451
 
443
452
  ## Documents
444
453
 
445
- - [Architecture and threat model](https://github.com/mangybyte/leashbyte/blob/main/docs/DESIGN.md)
446
- - [Known limits and next steps](https://github.com/mangybyte/leashbyte/blob/main/docs/ROADMAP.md)
447
- - [Changelog](https://github.com/mangybyte/leashbyte/blob/main/CHANGELOG.md)
448
- - [Third-party licences](https://github.com/mangybyte/leashbyte/blob/main/docs/THIRD_PARTY.md)
449
- - [Python licence inventory](https://github.com/mangybyte/leashbyte/blob/main/docs/python-licenses.json)
450
- - [JavaScript licence inventory](https://github.com/mangybyte/leashbyte/blob/main/sdk/typescript/THIRD_PARTY_LICENSES.json)
451
- - [Security policy](https://github.com/mangybyte/leashbyte/blob/main/SECURITY.md)
452
- - [Contributing](https://github.com/mangybyte/leashbyte/blob/main/CONTRIBUTING.md)
454
+ - [Architecture and threat model](https://github.com/mangybyte/leashbyte/blob/v0.1.2/docs/DESIGN.md)
455
+ - [Known limits and next steps](https://github.com/mangybyte/leashbyte/blob/v0.1.2/docs/ROADMAP.md)
456
+ - [Changelog](https://github.com/mangybyte/leashbyte/blob/v0.1.2/CHANGELOG.md)
457
+ - [Third-party licences](https://github.com/mangybyte/leashbyte/blob/v0.1.2/docs/THIRD_PARTY.md)
458
+ - [Python licence inventory](https://github.com/mangybyte/leashbyte/blob/v0.1.2/docs/python-licenses.json)
459
+ - [JavaScript licence inventory](https://github.com/mangybyte/leashbyte/blob/v0.1.2/sdk/typescript/THIRD_PARTY_LICENSES.json)
460
+ - [Security policy](https://github.com/mangybyte/leashbyte/blob/v0.1.2/SECURITY.md)
461
+ - [Contributing](https://github.com/mangybyte/leashbyte/blob/v0.1.2/CONTRIBUTING.md)
453
462
 
454
463
  ## Licence
455
464
 
456
- LeashByte is licensed under the [Apache License 2.0](https://github.com/mangybyte/leashbyte/blob/main/LICENSE). Copyright 2026 MangyByte Ltd. See [NOTICE](https://github.com/mangybyte/leashbyte/blob/main/NOTICE) and the [third-party licences](https://github.com/mangybyte/leashbyte/blob/main/docs/THIRD_PARTY.md) for dependency notices.
465
+ LeashByte is licensed under the [Apache License 2.0](https://github.com/mangybyte/leashbyte/blob/v0.1.2/LICENSE). Copyright 2026 MangyByte Ltd. See [NOTICE](https://github.com/mangybyte/leashbyte/blob/v0.1.2/NOTICE) and the [third-party licences](https://github.com/mangybyte/leashbyte/blob/v0.1.2/docs/THIRD_PARTY.md) for dependency notices.
@@ -2,7 +2,7 @@
2
2
 
3
3
  LeashByte is a self-hosted toolkit that gives AI agents access to the web. It puts search, page fetching, real Chrome sessions, an encrypted credential vault and goal-driven agent runs behind one REST API, with an MCP server and Python and TypeScript SDKs on top. It's meant for developers who want their agents to search, read and use websites from their own machines, driven by a model they choose. A local model works fine.
4
4
 
5
- LeashByte is pre-alpha, so expect rough edges and breaking changes. The services run with Docker Compose from a source checkout. The Python SDK is on PyPI as `leashbyte-sdk`, and the server package as `leashbyte`.
5
+ LeashByte is pre-alpha, so expect rough edges and breaking changes. The services run with Docker Compose from a source checkout. The Python SDK is on PyPI as `leashbyte-sdk`, and the server package as `leashbyte`. The TypeScript SDK is on npm as `leashbyte`.
6
6
 
7
7
  The project home is [leashbyte.com](https://leashbyte.com).
8
8
 
@@ -127,28 +127,27 @@ with LeashByteClient() as client:
127
127
 
128
128
  The client reads `LEASHBYTE_API_KEY` or `LEASHBYTE_API_KEY_FILE`. It doesn't read `LEASHBYTE_API_URL`, so pass `base_url` if the API isn't at the default `http://127.0.0.1:8080`.
129
129
 
130
- The client keeps its configured key out of `repr` and API errors. It can't do the same for your own logging, so keep request bodies, screenshots, page content and run artifacts out of your logs. There's a run example in [`sdk/python/README.md`](https://github.com/mangybyte/leashbyte/blob/main/sdk/python/README.md).
130
+ The client keeps its configured key out of `repr` and API errors. It can't do the same for your own logging, so keep request bodies, screenshots, page content and run artifacts out of your logs. There's a run example in [`sdk/python/README.md`](https://github.com/mangybyte/leashbyte/blob/v0.1.2/sdk/python/README.md).
131
131
 
132
132
  ## TypeScript SDK
133
133
 
134
- The TypeScript SDK lives in `sdk/typescript`. Its [README](https://github.com/mangybyte/leashbyte/blob/main/sdk/typescript/README.md) has the install and usage details. To build it from the checkout:
134
+ The TypeScript SDK is on npm. It has no runtime npm dependencies and uses Node's built-in `fetch` API.
135
135
 
136
136
  ```bash
137
- npm ci --prefix sdk/typescript
138
- npm --prefix sdk/typescript run build
137
+ npm install leashbyte
139
138
  ```
140
139
 
141
- Then import `LeashByteClient` from `sdk/typescript/dist/src/index.js`. It has no runtime npm dependencies and uses Node's built-in `fetch` API.
142
-
143
140
  ```typescript
144
- import { LeashByteClient } from "./sdk/typescript/dist/src/index.js";
141
+ import { LeashByteClient } from "leashbyte";
145
142
 
146
143
  const client = new LeashByteClient();
147
144
  const page = await client.fetchPage({ url: "https://example.com/" });
148
145
  console.log(page.status, page.final_url);
149
146
  ```
150
147
 
151
- It reads `LEASHBYTE_API_KEY` or `LEASHBYTE_API_KEY_FILE`. Pass `baseUrl` to the constructor for a different API address. The configured key is redacted from inspection, JSON serialization and API errors.
148
+ The source lives in `sdk/typescript`. Its [README](https://github.com/mangybyte/leashbyte/blob/v0.1.2/sdk/typescript/README.md) has more usage details and shows how to build it from the checkout.
149
+
150
+ The client reads `LEASHBYTE_API_KEY` or `LEASHBYTE_API_KEY_FILE`. Pass `baseUrl` to the constructor for a different API address. The configured key is redacted from inspection, JSON serialization and API errors.
152
151
 
153
152
  ## Using the API
154
153
 
@@ -282,7 +281,17 @@ sudo ufw allow from 172.29.250.0/24 to 172.29.250.1 port 11434 proto tcp comment
282
281
 
283
282
  Change the port in the rule if you've changed `LEASHBYTE_LOCAL_MODEL_PORT`. The rule doesn't change the model's own listener, and other networks still can't reach the relay.
284
283
 
285
- Claude runs use `claude-haiku-5-5` through the official Anthropic SDK. Put an API key in a file outside the repository and point `LEASHBYTE_ANTHROPIC_API_KEY_HOST_FILE` at it, and Compose mounts it.
284
+ Claude runs use `claude-haiku-5-5` through the official Anthropic SDK. Put an API key in a file outside the repository and point `LEASHBYTE_ANTHROPIC_API_KEY_HOST_FILE` at it, and Compose mounts it read-only at `/run/anthropic.key` in the agent worker.
285
+
286
+ The worker runs as uid 10001 with every Linux capability dropped, and a bind mount keeps the host file's owner and mode. So a key file with mode `0600` that belongs to your own user can't be read inside the container. Give uid 10001 read access and keep everyone else out. On Linux, an ACL entry does that without changing the owner:
287
+
288
+ ```bash
289
+ KEY_FILE=/path/to/anthropic.key
290
+ chmod 600 "$KEY_FILE"
291
+ setfacl -m u:10001:r--,g::--- "$KEY_FILE"
292
+ ```
293
+
294
+ A later `chmod` that gives the group nothing also resets the ACL mask and takes the read entry away again, so run `setfacl` after it. With rootless Docker or Podman, uid 10001 in the container maps to a different uid on the host, so give that uid access instead. If you don't have `setfacl`, `sudo chown 10001 "$KEY_FILE"` with mode `0400` works too. When the worker can't read the key, it logs `Claude runs are unavailable` at start, and every Claude run fails with an error that names `LEASHBYTE_ANTHROPIC_API_KEY_FILE` and the reason, such as `Permission denied`.
286
295
 
287
296
  Create a run with fixed limits:
288
297
 
@@ -372,9 +381,9 @@ The hook runs after the URL, network, robots and rate-limit checks. It receives
372
381
 
373
382
  ## Configuration
374
383
 
375
- [`.env.example`](https://github.com/mangybyte/leashbyte/blob/main/.env.example) has the main settings. Every application secret also has a `_FILE` variant for container secrets. The API won't start without an API key, and the vault won't start without a 32-byte master key.
384
+ [`.env.example`](https://github.com/mangybyte/leashbyte/blob/v0.1.2/.env.example) has the main settings. Every application secret also has a `_FILE` variant for container secrets. The API won't start without an API key, and the vault won't start without a 32-byte master key.
376
385
 
377
- The OpenAPI schema is in [`openapi.json`](https://github.com/mangybyte/leashbyte/blob/main/openapi.json).
386
+ The OpenAPI schema is in [`openapi.json`](https://github.com/mangybyte/leashbyte/blob/v0.1.2/openapi.json).
378
387
 
379
388
  ## Stopping the services
380
389
 
@@ -414,15 +423,15 @@ The GitHub Actions workflow runs the same checks. It also starts the Compose sta
414
423
 
415
424
  ## Documents
416
425
 
417
- - [Architecture and threat model](https://github.com/mangybyte/leashbyte/blob/main/docs/DESIGN.md)
418
- - [Known limits and next steps](https://github.com/mangybyte/leashbyte/blob/main/docs/ROADMAP.md)
419
- - [Changelog](https://github.com/mangybyte/leashbyte/blob/main/CHANGELOG.md)
420
- - [Third-party licences](https://github.com/mangybyte/leashbyte/blob/main/docs/THIRD_PARTY.md)
421
- - [Python licence inventory](https://github.com/mangybyte/leashbyte/blob/main/docs/python-licenses.json)
422
- - [JavaScript licence inventory](https://github.com/mangybyte/leashbyte/blob/main/sdk/typescript/THIRD_PARTY_LICENSES.json)
423
- - [Security policy](https://github.com/mangybyte/leashbyte/blob/main/SECURITY.md)
424
- - [Contributing](https://github.com/mangybyte/leashbyte/blob/main/CONTRIBUTING.md)
426
+ - [Architecture and threat model](https://github.com/mangybyte/leashbyte/blob/v0.1.2/docs/DESIGN.md)
427
+ - [Known limits and next steps](https://github.com/mangybyte/leashbyte/blob/v0.1.2/docs/ROADMAP.md)
428
+ - [Changelog](https://github.com/mangybyte/leashbyte/blob/v0.1.2/CHANGELOG.md)
429
+ - [Third-party licences](https://github.com/mangybyte/leashbyte/blob/v0.1.2/docs/THIRD_PARTY.md)
430
+ - [Python licence inventory](https://github.com/mangybyte/leashbyte/blob/v0.1.2/docs/python-licenses.json)
431
+ - [JavaScript licence inventory](https://github.com/mangybyte/leashbyte/blob/v0.1.2/sdk/typescript/THIRD_PARTY_LICENSES.json)
432
+ - [Security policy](https://github.com/mangybyte/leashbyte/blob/v0.1.2/SECURITY.md)
433
+ - [Contributing](https://github.com/mangybyte/leashbyte/blob/v0.1.2/CONTRIBUTING.md)
425
434
 
426
435
  ## Licence
427
436
 
428
- LeashByte is licensed under the [Apache License 2.0](https://github.com/mangybyte/leashbyte/blob/main/LICENSE). Copyright 2026 MangyByte Ltd. See [NOTICE](https://github.com/mangybyte/leashbyte/blob/main/NOTICE) and the [third-party licences](https://github.com/mangybyte/leashbyte/blob/main/docs/THIRD_PARTY.md) for dependency notices.
437
+ LeashByte is licensed under the [Apache License 2.0](https://github.com/mangybyte/leashbyte/blob/v0.1.2/LICENSE). Copyright 2026 MangyByte Ltd. See [NOTICE](https://github.com/mangybyte/leashbyte/blob/v0.1.2/NOTICE) and the [third-party licences](https://github.com/mangybyte/leashbyte/blob/v0.1.2/docs/THIRD_PARTY.md) for dependency notices.
@@ -4,7 +4,7 @@ LeashByte is pre-alpha. Please don't use it to process sensitive data yet.
4
4
 
5
5
  ## Reporting a vulnerability
6
6
 
7
- Email `security@leashbyte.com`, and please don't open a public issue for a suspected vulnerability.
7
+ Use GitHub's [private report form](https://github.com/mangybyte/leashbyte/security/advisories/new) or email `security@leashbyte.com`, and please don't open a public issue for a suspected vulnerability.
8
8
 
9
9
  Tell us the affected version, how to reproduce the problem and what you think the impact is. Logs help, but take credentials and personal data out of them first.
10
10
 
@@ -1,6 +1,6 @@
1
1
  # LeashByte design
2
2
 
3
- This document describes how LeashByte is put together: the services, how requests flow through them, the agent loop, the vault, and the threat model behind the security choices. LeashByte is pre-alpha. The stack is meant to run on your own machine or network, and the PyPI and npm packages and the public site aren't out yet.
3
+ This document describes how LeashByte is put together: the services, how requests flow through them, the agent loop, the vault, and the threat model behind the security choices. LeashByte is pre-alpha. The stack is meant to run on your own machine or network.
4
4
 
5
5
  ## What it is for
6
6
 
@@ -161,10 +161,15 @@ The browser layer builds an accessibility snapshot and gives each actionable ele
161
161
  - The user's goal and the current run limits.
162
162
  - The current page origin and title.
163
163
  - A compact accessibility tree with numbered marks.
164
+ - The rendered text of the page, in reading order.
164
165
  - The last accepted actions and their results.
165
166
  - Credential aliases, when the page origin is allowed for them.
166
167
 
167
- The model doesn't get screenshots. A text-only local model has to be able to finish a run from the accessibility tree alone, and that is the case we design for.
168
+ The page text is the rendered `innerText` of the document body, so it follows the layout and skips elements with `display: none` or `visibility: hidden`. Text hidden in other ways, such as with `opacity: 0`, still comes through, which is one more reason to treat it as untrusted. It covers the whole page, not just the viewport, so scrolling only changes it on pages that load more content as you scroll. Text inside frames isn't included. We collapse runs of spaces and blank lines, then cut the text at 4,000 characters and set `text_truncated` when we cut it. In this release the model can't read past that cut. The marked elements give the model something to act on, and the text gives it something to read: without the text, a model asked about a paragraph or a price only sees link and button names, and it will either give up or guess. The system prompt tells it to answer only from the observation and to fail when the answer isn't there.
169
+
170
+ The page script reads up to 100,000 characters, and we redact secret values from that before we collapse whitespace and make the 4,000 character cut, the same way as element names. The script runs inside the page, so the server applies the 100,000 limit again rather than trust it. If the script had to cut the text, a secret could sit across that first cut where redaction can't match it, so we also drop a tail as long as the longest form of any secret. The text counts toward the run's token budget like the rest of the observation, and it is stored with each step's observation in the run record.
171
+
172
+ The model doesn't get screenshots. A text-only local model has to be able to finish a run from the accessibility tree and the page text alone, and that is the case we design for.
168
173
 
169
174
  Page text is untrusted. The prompt marks it as data, and it never becomes a system instruction.
170
175
 
@@ -30,5 +30,3 @@ LeashByte is pre-alpha. These are the gaps we know about and the work we plan to
30
30
  - The static site has no dependency licence inventory yet.
31
31
  - Third-party GitHub Actions and container images should be pinned by digest.
32
32
  - Mail to the leashbyte.com addresses hasn't been verified end to end yet.
33
- - The PyPI and npm packages aren't published yet.
34
- - The project site and the first tagged release are next.
@@ -151,7 +151,7 @@
151
151
  },
152
152
  {
153
153
  "name": "leashbyte-sdk",
154
- "version": "0.1.1",
154
+ "version": "0.1.2",
155
155
  "license": "Apache-2.0"
156
156
  },
157
157
  {
@@ -3,7 +3,7 @@
3
3
  "info": {
4
4
  "title": "LeashByte",
5
5
  "description": "Self-hosted search, page fetch, browser, and vault APIs.",
6
- "version": "0.1.1"
6
+ "version": "0.1.2"
7
7
  },
8
8
  "paths": {
9
9
  "/healthz": {
@@ -1301,6 +1301,16 @@
1301
1301
  },
1302
1302
  "type": "array",
1303
1303
  "title": "Nodes"
1304
+ },
1305
+ "text": {
1306
+ "type": "string",
1307
+ "title": "Text",
1308
+ "default": ""
1309
+ },
1310
+ "text_truncated": {
1311
+ "type": "boolean",
1312
+ "title": "Text Truncated",
1313
+ "default": false
1304
1314
  }
1305
1315
  },
1306
1316
  "type": "object",
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "leashbyte"
3
- version = "0.1.1"
3
+ version = "0.1.2"
4
4
  description = "Self-hosted search and page fetch APIs"
5
5
  readme = "README.md"
6
6
  requires-python = ">=3.13,<3.14"
@@ -13,7 +13,7 @@ dependencies = [
13
13
  "fastapi>=0.121,<1",
14
14
  "httpcore>=1.0.9,<1.1",
15
15
  "httpx>=0.28,<1",
16
- "leashbyte-sdk>=0.1.1,<0.2",
16
+ "leashbyte-sdk>=0.1.2,<0.2",
17
17
  "mcp>=1.26,<2",
18
18
  "playwright>=1.56,<2",
19
19
  "pydantic-settings>=2.11,<3",
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "leashbyte-sdk"
3
- version = "0.1.1"
3
+ version = "0.1.2"
4
4
  description = "Python client for the LeashByte API"
5
5
  readme = "README.md"
6
6
  requires-python = ">=3.13,<3.14"
@@ -91,6 +91,8 @@ class BrowserSnapshotResponse(BaseModel):
91
91
  url: Annotated[str, Field(title="Url")]
92
92
  title: Annotated[str, Field(title="Title")]
93
93
  nodes: Annotated[list[BrowserNode], Field(title="Nodes")]
94
+ text: Annotated[str | None, Field(title="Text")] = ""
95
+ text_truncated: Annotated[bool | None, Field(title="Text Truncated")] = False
94
96
 
95
97
 
96
98
  class CancelRunRequest(BaseModel):
@@ -2,21 +2,18 @@
2
2
 
3
3
  A TypeScript client for the stable LeashByte REST API. It uses types generated from the OpenAPI schema and Node's built-in `fetch` API, and it has no runtime npm dependencies.
4
4
 
5
- The npm package isn't published yet, so build it from a GitHub checkout.
5
+ ## Install
6
6
 
7
- ## Build
8
-
9
- You'll need Node 20 or later.
7
+ You'll need Node 20 or later. The package is ESM only.
10
8
 
11
9
  ```bash
12
- npm ci
13
- npm run build
10
+ npm install leashbyte
14
11
  ```
15
12
 
16
13
  ## Use
17
14
 
18
15
  ```typescript
19
- import { LeashByteClient } from "./dist/src/index.js";
16
+ import { LeashByteClient } from "leashbyte";
20
17
 
21
18
  const client = new LeashByteClient({
22
19
  baseUrl: "http://127.0.0.1:8080",
@@ -37,11 +34,17 @@ The client reads `LEASHBYTE_API_KEY` or `LEASHBYTE_API_KEY_FILE`. You can pass `
37
34
 
38
35
  The configured key is redacted from inspection, JSON serialization and API errors. Binary methods return a `Uint8Array`. Screenshots and run artifacts can contain page data, so keep them in private storage. For browser logins, use credential placeholders. Passwords don't belong in goals, URLs or ordinary text actions.
39
36
 
40
- ## Checks
37
+ ## Build from a checkout
38
+
39
+ To work on the SDK itself, clone https://github.com/mangybyte/leashbyte and run these in `sdk/typescript`:
41
40
 
42
41
  ```bash
42
+ npm ci
43
+ npm run build
43
44
  npm test
44
45
  npm run licenses
45
46
  ```
46
47
 
48
+ The build writes the package to `dist/src`. To build exactly this version, check out the `v0.1.2` tag. It has the same SDK code as this package.
49
+
47
50
  `npm run licenses` checks the development dependencies and writes `THIRD_PARTY_LICENSES.json`. The schema types are generated from `openapi.json` at the repository root, so run `npm run generate` whenever that file changes.
@@ -1,12 +1,12 @@
1
1
  {
2
2
  "name": "leashbyte",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "lockfileVersion": 3,
5
5
  "requires": true,
6
6
  "packages": {
7
7
  "": {
8
8
  "name": "leashbyte",
9
- "version": "0.1.1",
9
+ "version": "0.1.2",
10
10
  "license": "Apache-2.0",
11
11
  "devDependencies": {
12
12
  "@types/node": "^25.0.0",