entinyGram Plugins & SDK

The official plugin catalog, feature plugins, and developer SDK for entinyGram, an advanced Android fork of Inugram.

Architecture & Design Philosophy

entinyGram inherits Inugram's plugin engine: standalone .inu.js bundles executed in a sandboxed QuickJS runtime with granular user-approved permissions (grants) and access to Android APIs (inu.ui, inu.jvm, inu.xposed, inu.io).

Instead of baking custom functionality directly into the Android application codebase, entinyGram's features are designed and built as modular plugins:

┌────────────────────────────────────────────────────────┐
│               Inugram Plugin Engine                    │
│        (QuickJS runtime, grant sandbox, hooks)         │
├────────────────────────────────────────────────────────┤
│                   entinyGram App                       │
│        (Lightweight glue layer & install bridge)       │
├────────────────────────────────────────────────────────┤
│               entinyGram SDK Plugin                    │
│      (entinygram.sdk: Marketplace UI & Embed Engine)   │
├────────────────────────────────────────────────────────┤
│                  Feature Plugins                       │
│  2GIS  │  Calendar Systems  │  Text Animation  │  ...  │
└────────────────────────────────────────────────────────┘

Why this architecture?

Upstream Maintainability: Upstream Telegram and Inugram releases can be merged cleanly with minimal patchsets.
Instant Updates: Plugins update independently via GitHub and the in-app Marketplace—no APK re-download or reinstall required.
User Transparency & Choice: Every plugin explicitly declares its required grants (fetch, unsafe.jvm, unsafe.xposed). Users decide what to run.
Clean Decoupling: If a plugin fails or is disabled, the core Telegram client continues to function normally.

The SDK Dependency System

All official feature plugins require the entinyGram SDK plugin (entinygram.sdk):

// @requires entinygram.sdk >=0.1.0-alpha

How the app enforces dependencies:

Installation Guard (PluginManager.kt:329): When installing a plugin via file, marketplace, or ADB, the app checks PluginDependencies.unmet(manifest). If entinygram.sdk is missing, disabled, or outdated, installation is refused immediately with an explanatory bulletin:
- "Needs the plugin entinygram.sdk. Install it first" (InuPluginsErrorRequires)
- "Needs entinygram.sdk 0.1.0-alpha or newer" (InuPluginsErrorRequiresVersion)
Runtime Lifecycle Guard: If a user disables entinygram.sdk in settings, stopUnmet() immediately suspends all dependent plugins. When the SDK is re-enabled, retryUnmet() automatically restores them.
Settings Entrypoint: The SDK plugin carries the runtime embed engine (@entiny/sdk/embed). Without it, feature plugins cannot mount their custom rows, switches, or pickers into native Telegram menus.

Official Plugins

Plugin	Package ID	Version	Requires	Description
entinyGram SDK	`entinygram.sdk`	`0.1.2-beta`	None	In-app Marketplace UI and shared settings embedding engine.
Text Animation	`entinygram.text-animation`	`1.0.0`	`SDK`	Fluid typing feedback animations and particle burst effects on backspace/deletion.
2GIS	`entinygram.2gis`	`1.0.0`	`SDK`	High-resolution 2GIS raster map tiles and location preview images (requires API key).
Calendar Systems	`entinygram.calendar-systems`	`1.1.0`	`SDK`	Alternative calendar formatting (Hijri, Persian, Indian, Hebrew, Buddhist, etc.) for dates.
Doc Viewer	`entinygram.doc-viewer`	`1.1.0`	`SDK`	In-app viewer for PDF, DOCX, XLSX, text, code, images, archives and more.
Call Avatar	`entinygram.call-avatar`	`1.1`	`SDK`	Full-screen caller photo, display timing modes, translucent voice-call buttons, and uk/en/ru settings.
Yandex	`entinygram.yandex`	`1.0.0`	`SDK`	In-app translation via Yandex Cloud Translate v2 and Yandex static map previews.

User Repository

Besides the official catalog the marketplace shows a separate User plugins section backed by plugins/user/index.json. It is the place for community plugins that are distributed as ready-made .inu.js bundles instead of being built from source in this repo.

To add or update a user plugin:

Drop the ready-made bundle into plugins/user/bundles/ with proper @id, @version and @description in its ==InuPlugin== header.
Add @id matching plugins/user/icons/<id>.svg for the marketplace icon.
Run bun run build:user — it hashes the bundle, publishes an immutable copy to plugins/user/dist/<id>/<version>.inu.js and refreshes the index.
Commit. The marketplace picks the plugin up from <repo>/main/plugins/user/index.json.

Current user plugins:

Plugin	ID	Version	Author	Description
Display Resize	`user.display-resize`	`1.0.0`	Pixuz	Control the full size of Telegram's UI (scale density) with presets and a custom factor.
Hide Folder Tags	`user.hide-folder-tags`	`1.1.0`	Pixuz	Hide the colored folder badges (SH, BOT, GR, CH…) under chat names.
Local Message Edit	`user.local-message-edit`	`1.7.0`	Pixuz	Local edit/reset of message text in chats, groups, channels and bots.

Installing Plugins

1. In-App Marketplace (Recommended)

Open Settings → Plugins → Marketplace.

Browse available plugins with live descriptions, version history, and icons, split into the entinyGram (official) and User plugins (community repository) sections.
Tap Install or Update. The app downloads the script, validates its SHA-256 against the catalog, and prompts you to review the requested grants.
On a plugin page, an About card shows the description, author, source repository, plugin ID (tap to copy), requirements and the latest version.

2. Loading from a File

Transfer any .inu.js file to your Android device and open it via Settings → Plugins → Load from file or by tapping the file in a chat.

3. Developer Push (ADB)

Enable Developer mode under Settings → Plugins on your device, then push plugins directly from your workstation:

bun inu push

Developing Plugins

Prerequisites

Bun runtime installed.
Android device or emulator with entinyGram installed and Developer Mode enabled in Settings → Plugins.

# Clone repository
git clone https://github.com/entinyGram/plugins.git
cd plugins

# Install dependencies
bun install

CLI Commands

Run commands inside a plugin directory (plugins/<name>):

Command	Action
`bun inu dev`	Watch files, auto-rebuild, push to device over ADB, and reload in real-time
`bun inu push`	Single build, deploy to device over ADB, and print execution logs
`bun inu build`	Typecheck and build release `.inu.js` file into `dist/`
`bun inu check`	Validate manifest schema, grants, and syntax
`bun inu eval "<code>"`	Evaluate an arbitrary JavaScript snippet inside the on-device QuickJS engine

Placing Plugin Settings in entinyGram

Using @entiny/sdk, any plugin can mount its settings controls directly into native Telegram screens:

import { defineConfig } from '@inugram/cli'
import { withEntiny } from '@entiny/sdk'

export default defineConfig({
  plugins: {
    'my-plugin': {
      entry: 'src/index.ts',
      manifest: withEntiny({
        id: 'entinygram.my-plugin',
        name: 'My Plugin',
        author: 'entinyGram',
        version: '1.0.0',
        description: 'Demonstrates settings placement',
        grants: ['unsafe.jvm', 'unsafe.xposed'],
      }, {
        // 1. Adds a row that navigates to the plugin's full settings screen:
        screen: ['category-chats'],
        // 2. Draws inline switches/sliders at the end of a section:
        inline: [{ slot: 'category-chats.end', rows: ['my_feature_switch'] }],
        // 3. Adds radio options to dialog pickers:
        choice: [{ slot: 'behavior.map-provider', rows: ['my_tile_option'] }],
      }),
    },
  },
})

withEntiny(...) automatically appends @requires entinygram.sdk >=0.1.0-alpha and builds the manifest metadata directives (@entiny-menu, @entiny-inline, @entiny-choice).

Available slot identifiers are cataloged in sdk/entiny/slots.json and typed in sdk/entiny/src/slots.ts.

Publishing to the Catalog

Ensure the plugin resides in plugins/features/<name> (translations in plugins/locales/<name>) with an inu.config.ts, icon.svg (24×24 single-color), and README.md.
Build and update the catalog:
```
bun run build:plugins
```
This compiles all plugins into plugins/dist/<id>/entinyGram-<Name>-<version>.inu.js, computes their SHA-256 hashes, and refreshes plugins/index.json and index.json.
Commit and push your changes to GitHub. The in-app marketplace automatically detects published updates.

Named bundles and the manual workflow

bun run pack copies every published bundle as <Name>-<version>.inu.js into release/, checking each against the catalog hash (bun run pack:rebuild builds from source first) (for example entinyGram-SDK-0.1.2-beta.inu.js). The Build plugins workflow (Actions → Build plugins → Run workflow) does this on demand: pick one plugin or all of them, and optionally commit the refreshed catalog or publish the bundles as a GitHub release.

Repository Structure

├── index.json             # Root catalog read by the app (paths relative to root)
├── plugins/
│   ├── index.json         # Catalog for the marketplace (paths relative to plugins/)
│   ├── dist/              # Published immutable .inu.js release files
│   ├── core/marketplace/  # The entinygram.sdk plugin: marketplace UI and settings embedding (not the @entiny/sdk library)
│   ├── features/          # Feature plugins (2gis, calendar-systems, call-avatar, doc-viewer, text-animation, yandex)
│   ├── locales/           # Translation packs, one plugin per language (locale-<iso>)
│   └── user/              # Community "User plugins" marketplace section
│       ├── index.json     # User catalog read by the marketplace
│       ├── bundles/       # Ready-made .inu.js bundles (source of truth)
│       ├── icons/         # Marketplace icons, one per plugin id
│       └── dist/          # Published immutable copies of user bundles
├── sdk/
│   ├── entiny/            # @entiny/sdk: settings placement, slots, map utilities
│   ├── cli/               # @inugram/cli tooling
│   ├── types/             # @inugram/plugin-types typings
│   └── docs/              # Guides for engine APIs (grants, UI, JVM, Xposed)
└── scripts/
    ├── build-plugin-index.ts # Compiles official plugins and regenerates index.json
    ├── build-user-index.ts   # Publishes user bundles and regenerates plugins/user/index.json
    └── generate-slots.ts     # Extracts available settings slots from app strings

License & Credits

Licensed under GPL-2.0-or-later, matching entinyGram and Inugram (see LICENSE).

entinyGram: The independent power-user Telegram Android fork.
Inugram by @teidesu: The plugin engine, QuickJS bindings, and foundation toolchain.

Navigation Menu

Repository navigation

About

Repository files navigation

entinyGram Plugins & SDK

Architecture & Design Philosophy

Why this architecture?

The SDK Dependency System

How the app enforces dependencies:

Official Plugins

User Repository

Installing Plugins

1. In-App Marketplace (Recommended)

2. Loading from a File

3. Developer Push (ADB)

Developing Plugins

Prerequisites

CLI Commands

Placing Plugin Settings in entinyGram

Publishing to the Catalog

Named bundles and the manual workflow

Repository Structure

License & Credits

About

Releases

Packages

Contributors

Languages

Name		Name	Last commit message	Last commit date
.claude/skills/inugram-plugin-port		.claude/skills/inugram-plugin-port
.github/workflows		.github/workflows
plugins		plugins
scripts		scripts
sdk		sdk
.gitignore		.gitignore
README.md		README.md
bun.lock		bun.lock
index.json		index.json
package.json		package.json

Latest commit

History

Folders and files

Repository files navigation

entinyGram Plugins & SDK

Architecture & Design Philosophy

Why this architecture?

The SDK Dependency System

How the app enforces dependencies:

Official Plugins

User Repository

Installing Plugins

1. In-App Marketplace (Recommended)

2. Loading from a File

3. Developer Push (ADB)

Developing Plugins

Prerequisites

CLI Commands

Placing Plugin Settings in entinyGram

Publishing to the Catalog

Named bundles and the manual workflow

Repository Structure

License & Credits

About

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages