tessl 0.81.3 → 0.83.0

package/README.md

@@ -1,33 +1,93 @@
-# Tessl
+# M: The CLI that briefs your agents
 
-Tessl is an Agent Enablement Platform that gives your agents the context they're missing.
+![007-M](./m.png)
 
-- Install usage docs for your favorite open source library from the Tessl Spec Registry
-- Create your own internal docs and share with your team 
+## Overview
 
-**Explore more in our [official documentation](https://docs.tessl.io)**.
+`m` is a CLI that also serves as an MCP (Model Context Protocol) server for AI agents. It manages local context steering, agent steering, and CLI tools to manage plugins and workspaces.
 
-Visit the [Registry](https://tessl.io/registry) to see which open source libraries we provide documentation for.
+The CLI acts as a bridge between your local development environment and the Tessl platform, providing agents with the context they need to be effective in your project.
 
-## Get started
+## Key Features
 
-1. Install Tessl:
+- **MCP Server**: Exposes tools for AI agents to interact with your local plugins and get contextual recommendations
+- **Project Setup**: search and install plugins relevant to your project.
+- **Workspace Operations**: Create and manage workspaces, handle team members.
+- **Plugin Management**: publish and archive plugins in the registry.
 
-```sh
-curl -fsSL https://get.tessl.io | sh
+## Development
+
+### Environment Setup
+
+This will install the dependencies for a dev environment:
+
+```bash
+  ./scripts/setup.sh
+  bun install
 ```
 
-2. Now in your project directory run `tessl`
+Functionally, the setup script installs brew, runs `brew bundle` and copies the .env if it is missing.
+
+### WorkOS setup for workspace and plugin publishing development
+
+> [!WARNING]
+> `m` runs against Tessl's API and WorkOS in production by default, which minimises setup and works well for read-only use cases.
 
-## Reporting Bugs
+If you're testing workspace-related or plugin publishing functionality, you probably want to run against the development API instead.
+You can do this by following the setup instructions for running via Tilt in the [backend repo](https://github.com/tesslio/backend) and copying `TESSL_API_BASE_URL` and `WORKOS_CLIENT_ID` from [.env.example](./.env.example) to point the CLI at it.
 
-We love feedback. You can use the `tessl feedback` command to report issues or share feedback directly within Tessl, file a [GitHub issue](https://github.com/tesslio/cli/issues) or just email <support@tessl.io>.
+### Useful Commands
+
+```bash
+bun dev # Run the CLI in dev mode
+bun mcp # Run the MCP server in dev mode
+bunx @modelcontextprotocol/inspector bun mcp # Inspect the MCP server
+
+bun format  # Format
+bun lint    # Lint source code (typecheck + oxlint + ast-grep)
+bun test    # Run the test suite
+bun flat    # Convenience: runs format, lint and test
+```
+
+To run the dev CLI from outside the `m` directory, symlink `contrib/tessl-local.sh` to your PATH:
+
+```bash
+ln -s /path/to/m/contrib/tessl-local.sh /usr/local/bin/tessl-local
+tessl-local api /v1/workspaces   # works from anywhere
+```
+
+The script resolves its own location (even through symlinks), loads `.env` from the project root, and runs from source.
+
+### Visual Integration Tests
+
+The CLI uses VHS (Video Home System) for visual integration testing. These tests record terminal sessions as code, validating CLI behavior and generating visual documentation.
+
+```bash
+bun tape workspace list              # Run specific test
+bun tape --all                       # Run all visual tests
+bun tape --all --format gif,mp4      # Generate video recordings
+```
+
+### Syncing API types
+
+To update the types in [src/infrastructure/api/types.ts](./src/infrastructure/api/types.ts) to match the backend, run:
+
+```sh
+bun update-client-types # Runs against dev, requires you to be running backend locally
+
+## Or to run against the production API
+bun update-client-types:prod
+```
 
-## Connect on Discord
+### Testing github actions locally
 
-You are welcome to join the [Tessl Discord](https://tessl.co/4eV736y) to connect with other developers using Tessl.
+1. `brew install act rancher-desktop`
+2. Add `NPM_TOKEN_TILEWORKS_READ=` (and other keys) to `.secrets`
+   - use your `~/.npmrc` for your npm token. 1password likely has the other keys
+3. `export DOCKER_HOST=$(docker context inspect --format '{{.Endpoints.docker.Host}}')`
+4. Run `act` to test a workflow.
+   - eg: `act workflow_dispatch --job release --input tag="cli-release-nightly-251103" --artifact-server-path ./build`
 
-## Terms and Conditions
+## Contributing
 
-- [Terms of Service](https://tessl.io/policies/terms)
-- [Privacy Policy](https://tessl.io/policies/privacy-cookies)
+For detailed development guidelines, see [AGENTS.md](./AGENTS.md).

package/bin/tessl.js

@@ -327,7 +327,7 @@ function printUnsupportedPlatformMessage() {
 async function prepareBinary() {
   const tesslBinPath = getTesslBinPath();
   const existingBinary = await getExistingBinaryPath(tesslBinPath);
-  const installerVersion = "0.81.3";
+  const installerVersion = "0.83.0";
   const isTestOrDevBuild = installerVersion.includes("test") || installerVersion.includes("dev");
   let versionMismatch = false;
   if (isTestOrDevBuild && existingBinary) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tessl",
-  "version": "0.81.3",
+  "version": "0.83.0",
   "description": "Tessl CLI",
   "author": "Tessl",
   "license": "SEE LICENSE.md",