Date Period
May 06, 2026
@insites/logic-engine npm package — new TypeScript library that loads the rule and decision corpus, evaluates when/then decisions, renders scaffold templates, and exposes an MCP-server entry point.api/_external/v2/<resource>/<action>.json.liquid), with auth, method, status-code, error, and pagination conventions.path: front-matter alias.related_record + property accessors, write via record_create/record_update, multi-profile users.api_calls/, constants/, and form callback_actions. Worked Checkout Session example and webhook receiver shape.user_profile_types/ schemas are queried via related_record + property accessors, with multi-profile-type users called out explicitly.insites-ai-tools → insites-logic-engine to align with the npm package identifier @insites/logic-engine. Install URLs and the GitHub repository updated; the previous URLs remain redirected for a transition period.skills/insites/ for AI-tool consumption (Claude Code, OpenCode, Cursor) and engine/ + logic-engine/ for programmatic tooling.modules/<name>/public/{views,forms,graphql,authorization_policies,api_calls,schema,user_profile_types,emails,migrations,assets}/. New project-structure reference covers per-directory purpose, naming conventions, and module-prefixed render/include/graphql paths.callback_actions — form definitions at modules/<name>/public/forms/<name>.liquid are documented as the canonical pattern for create/update/delete operations: YAML schema for field declarations and per-field validation, a Liquid callback_actions block for GraphQL mutations and side effects. Worked update_password example covering form_set_error / form_set_field_error / form.errors.insites-cli help output (see also Bug Fix below).return true/false controllers; the platform compares the file's output as a string against the literal "true". Canonical examples now use single-line {%- ... -%} whitespace-trimmed Liquid that emits exactly true or false. Three concrete failure modes documented: trailing newline, returning a Liquid truthy object, and policy-name typos.prepack script that bundles the corpus into the published npm package, plus regex tightening on partial-resolution rules. 23/23 tests passing.insites-cli help output.master, but the repository's default branch is main. Corrected to main everywhere so install commands work.April 22, 2026
April 20, 2026
context.environment and context.location.host in background jobs: Background jobs now receive the same context.environment (e.g., production, staging) and context.location.host values that are available in web requests. This makes it easier to branch logic by environment or build host-aware URLs from asynchronous code.
skip_ssl_verification option for api_call_send: The api_call_send mutation accepts a new skip_ssl_verification boolean in its options. When set to true, SSL certificate verification is skipped for HTTPS requests - useful when integrating with internal services that use self-signed certificates. Disabled by default.
assign and function tags accept arguments in multiline.
assign tag supports string interpolation inside hash values.
[] and {} empty array/hash literals can be used as argument values.
pos-cli deploy improvements:
pos-cli 6.0.0+.pos-cli deploy --dry-run now includes assets: Dry-run mode reports which assets would be added or removed without uploading them. Requires pos-cli 6.0.0+.auto_manage_public_only_modules: true in config.yml): platformOS can now detect when a module contains only public files and, when it does, treat those files with the same lifecycle rules as regular application files - meaning files removed from the deploy are automatically deleted from the instance. Previously, module files were never deleted on deploy, which required adding each module name individually to the modules_that_allow_delete_on_deploy setting in the config. Because this changes deletion behaviour, it is disabled by default and must be explicitly opted into.Improved asset_manifest generation during pos-cli pull: greatly improves internal memory management and performance of generating asset_manifest (which includes all Assets). This also affects the Instance Clone feature.
Module handling — warning when a declared module is missing: If a module is listed in pos-modules.lock.json but its source files are missing from the deploy, a warning is now emitted.
Unknown app/config.yml properties are now warnings, not errors: If your config.yml contains a feature flag that does not exist in the target environment (for example when deploying from staging to a production environment that hasn't received that flag yet), the deploy no longer fails.
Better error messages for duplicate translation keys: When multiple translation files define the same key for the same locale, the reported error now lists each offending key alongside the specific files that defined it, instead of lumping all files together.
Duplicate model name detection on deploy: If two Model Schemas, Profile Types, or User Profiles resolve to the same parameterized name, the deploy now fails fast with a clear error listing the conflicting name and the files that introduced it.
raw_url handling for cloned instances: When an asset's raw_url points at an instance CDN path (/instances/N/assets/...), the host and instance ID are now rewritten to match the current instance's CDN configuration. This fixes broken asset URLs on cloned instances. External raw_url values (without the instance path segment) continue to be served as-is.April 13, 2026
April 03, 2026
Deploy, manage, and interact with your Insites instances directly from Claude Desktop — no CLI installation or browser login required.
CloudShell is an MCP (Model Context Protocol) server that connects Claude Desktop to your live Insites instances over HTTP. It gives you a direct bridge between your AI assistant and your Insites environment, so you can deploy files, manage environment variables, check logs, and more - all from a single conversational interface.
Traditional Insites development workflows require switching between terminal commands, browser tabs, and deployment tools. CloudShell removes that friction. With a single connection, Claude can read from and write to your instance without you ever leaving the conversation.
This is particularly useful for:
| Capability | Description |
|---|---|
| Sync files | Push a single file to your instance immediately |
| Deploy | Batch deploy multiple files in one operation |
| View logs | Fetch instance logs for debugging |
| Manage environment variables | List, add, or update env vars |
| List modules | See which modules are installed on your instance |
CloudShell connects via a single endpoint and authenticates using your Insites console credentials passed as HTTP headers. Once configured in Claude Desktop, your AI assistant has direct access to your instance - no additional software to install.
For full setup instructions and tool reference, see the CloudShell documentation.
April 02, 2026
constants command: set, unset, and list constant variables on an instance.exec command: execute Liquid code or GraphQL queries directly on an instance without deploying files. Supports inline code and --file option.--json flag added across 11 commands for structured JSON output (constants list, exec graphql, exec liquid, logsv2 search, logsv2 searchAround, logsv2 alerts list/add/trigger, logsv2 reports, migrations list, modules list).authData guard in deploy and sync commands.report module throwing MODULE_NOT_FOUND error.March 30, 2026
ins-table Timezone Overlay formatting.ins-sidebar-item icon flickering issue on hover.March 30, 2026
log.action value.March 30, 2026
March 19, 2026
Insites AI Tools is a skill documentation package that teaches LLMs (Claude, GPT, etc.) how to write correct code for the Insites platform. When installed, AI assistants can help developers build pages, query data, create commands, handle authentication, deploy code, and follow Insites coding conventions — without hallucinating unsupported features.
GitHub repository: https://github.com/insites-io/insites-ai-tool/
Filter by
Date Period