openwiki

27 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

openwiki visualize command basic usage

The `openwiki visualize` command serves a local interactive node graph beside a live Markdown reader in your browser for exploring OpenWiki Markdown wikis. From a repository with an `openwiki/` directory, run `openwiki visualize` to start the server.

openwiki visualize default server address and port

The `openwiki visualize` command serves the wiki on `127.0.0.1:4321` by default and automatically opens the browser to the graph.

openwiki visualize picks up file edits automatically

Edits to wiki files are picked up automatically while the `openwiki visualize` server runs.

openwiki visualize command options and arguments

The `openwiki visualize` command accepts the following arguments and flags: | Argument / flag | Description | | --- | --- | | `[path]` | Wiki directory to serve. Defaults to `./openwiki` | | `--port <port>` | Preferred port. Defaults to `4321`. Increments if the port is already in use | | `--no-open` | Do not open the browser automatically |

openwiki visualize with custom port and no-open example

To visualize a wiki with a custom port and without automatically opening the browser, run: `openwiki visualize openwiki --port 4400 --no-open`

openwiki visualize with custom wiki directory example

To explore a personal wiki at a custom location, run: `openwiki visualize ~/.openwiki/wiki`

openwiki visualizer display components

The visualizer shows an interactive node graph of wiki concepts and the Markdown links between them, alongside a side-by-side live Markdown reader for the selected page.

openwiki visualizer excludes scaffolding files from graph

The visualizer does not show `INSTRUCTIONS.md` and other scaffolding files in the interactive node graph.

Version number format

LangChain, LangGraph, and Deep Agents use Semantic Versioning (MAJOR.MINOR.PATCH) format. Major versions indicate breaking API updates, minor versions add new features while maintaining backward compatibility, and patch versions fix bugs and minor issues.

API stability levels

APIs are classified into stability tiers: stable APIs (no prefix) are production-ready with backward compatibility guaranteed; beta APIs are feature-complete but may have minor changes based on feedback; alpha APIs are experimental and subject to significant changes; deprecated APIs will be removed in future major releases; internal APIs are marked with leading underscore (_) or documented as internal and may change.

Internal API exception for methods

Methods prefixed with underscore (_) that contain no implementation and are meant to be overridden by subclasses are considered part of the public API of LangChain, not internal APIs.

Major release contents

Major releases (e.g., 1.0.0 to 2.0.0) may include breaking API changes, removal of deprecated features, and significant architectural improvements. They are accompanied by detailed migration guides, automated migration tools when possible, and extended support for the previous major version.

Minor release contents

Minor releases (e.g., 1.0.0 to 1.1.0) include new features and capabilities, performance improvements, new optional parameters, and backward-compatible enhancements.

Patch release contents

Patch releases (e.g., 1.0.0 to 1.0.1) include bug fixes, security updates, documentation improvements, and performance optimizations without API changes.

Version support policy

The latest major version receives full support with active development (ACTIVE status). The previous major version receives security updates and critical bug fixes for 12 months after the next major release (MAINTENANCE status). Older versions receive community support only.

LangChain 1.0 LTS release

LangChain 1.0 is designated as a long-term support (LTS) release. Version 1.0 will remain in ACTIVE status until version 2.0 is released. After version 2.0 is released, version 1.0 will enter MAINTENANCE mode for at least 1 year.

LangGraph 1.0 LTS release

LangGraph 1.0 is designated as a long-term support (LTS) release. Version 1.0 will remain in ACTIVE status until version 2.0 is released. After version 2.0 is released, version 1.0 will enter MAINTENANCE mode for at least 1 year.

Legacy versions maintenance timeline

Legacy versions LangChain 0.3 and LangGraph 0.4 are in MAINTENANCE mode until December 2026.

Check LangChain version Python

To check the installed LangChain version in Python, import langchain_core and print langchain_core.__version__.

Check LangGraph version Python

To check the installed LangGraph version in Python, import langgraph and print langgraph.__version__.

Check LangChain version JavaScript

To check the installed LangChain version in JavaScript, import version from 'langchain/package.json' and log it with console.log(version).

Check LangGraph version JavaScript

To check the installed LangGraph version in JavaScript, import version from '@langchain/langgraph/package.json' and log it with console.log(version).

Upgrade LangChain Python

To upgrade LangChain in Python to the latest version, run 'pip install -U langchain-core langchain'. To upgrade to a specific version, run 'pip install langchain-core==1.0.0'.

Upgrade LangGraph Python

To upgrade LangGraph in Python to the latest version, run 'pip install -U langgraph'. To upgrade to a specific version, run 'pip install langgraph==1.0.0'.

Upgrade LangChain JavaScript

To upgrade LangChain in JavaScript to the latest version, run 'npm update langchain @langchain/core'. To install a specific version, run 'npm install langchain@1.0.0 @langchain/core@1.0.0'.

Upgrade LangGraph JavaScript

To upgrade LangGraph in JavaScript to the latest version, run 'npm update @langchain/langgraph'. To install a specific version, run 'npm install @langchain/langgraph@1.0.0'.

Pre-release version formats

Pre-release versions include alpha versions (e.g., 1.0.0a1) for early preview with significant changes expected, beta versions (e.g., 1.0.0b1) that are feature-complete with minor changes possible, and release candidates (e.g., 1.0.0rc1) for final testing before stable release.

Give your agent this brain