Banana Studio

by banana
5
4
3
2
1
Score: 50/100

Description

Reviews

No reviews yet.

Stats

0
stars
56
downloads
0
forks
20
days
7
days
7
days
1
total PRs
0
open PRs
0
closed PRs
1
merged PRs
0
total issues
0
open issues
0
closed issues
51
commits

README file from

Github

Banana Studio

Create covers and illustrations from Markdown articles in Obsidian desktop, preview platform versions, and publish to WeChat Official Account or X.

Desktop only · Obsidian 1.11.4 or later

Banana Studio is developed in its own repository, starting from Banana Design commit ce8aa777ed432b33b168068f922b620df813402f. The existing Git history, license, and third-party notices are retained.

Features

  • Cover and body illustrations from the current Markdown note, with separate formats, templates, dimensions, and visual styles
  • Planning and image services configured independently — Codex CLI or your own API connections (OpenAI, Anthropic, Gemini, OpenRouter, Seedream, and other OpenAI-compatible endpoints; Ollama and local loopback services also work)
  • Canvas text planned from the article, with inline editing before generation; region edit to change only a marked area of a generated cover
  • Article illustration planning with owned paragraph markers; insertion never silently appends images
  • WeChat Official Account rich-text preview and draft publishing for verified accounts, including an optional fixed-IP SSH relay
  • X (Twitter) thread publishing with AI rewrite or deterministic splitting, OAuth 1.0a or OAuth 2.0, and optional proxy / SSH relay
  • Interface language follows Obsidian (Simplified Chinese or English)

Installation

Install from the Obsidian Community directory, or search for Banana Studio in Obsidian’s Community plugins settings.

For manual installation, download main.js, manifest.json, and styles.css from the matching GitHub Release, copy them into <vault>/.obsidian/plugins/banana-studio/, and enable the plugin. You can also install TreyDong/banana-studio with BRAT.

Release 0.12.3 uses compact built-in previews so its main plugin file stays below the 5 MB Obsidian Sync Standard limit.

Banana Studio uses its own plugin ID (banana-studio), settings, and default image folder (附件/Banana Studio). Existing Banana Design settings, credentials, and history are not imported automatically. Use a separate test vault for initial checks.

Getting started

  1. Enable the plugin and run Open illustration workspace (banana-studio:open), or use the ribbon icon.
  2. Select a manuscript in 笔记 marked media_stage: 写作 (also supports 待发布 / 已发布 or media_kind: 稿件 / 文章), or explicitly choose a Markdown source in 资料 / existing clippings. Diary, company, and investment sources are always excluded, even when an old session exists. The workspace has two stages: Create images (Cover / Body illustrations) and Preview & publish (Original article / WeChat / X).
  3. Choose a format and template, enter a request, and generate candidates. Reference images can be picked from disk or the vault.
  4. Export a PNG, insert a cover, or confirm a planned illustration batch. Restarting the workspace clears the current view; saved images and history remain.

API credentials and publishing secrets use Obsidian SecretStorage. The plugin does not replace the Markdown editor or act as a general autonomous agent.

Workspace paths

Desktop reads ~/.config/banana/workspace.json for the matching vault. Manuscripts use notesDir, explicit reference selections use materialsDir, and generated images default to attachmentsDir/Banana Studio. Existing custom output folders are preserved. Only recognized old output defaults are replaced; there is no fallback to the former media or attachment directories. Material selections apply to the current view and are not silently restored from saved history. Private sessions remain stored locally but cannot enter the picker, generated-image history, or AI source selection.

The companion banana-reader/scripts/workspace-migration.mjs exports migrateStudioData and migratePublicationData for applying an explicit old-to-new path map to session keys, image references, and separate publication records. These functions return copies, preserve unknown settings, and refuse key collisions. Stop the plugin before applying a reviewed result; do not let a running view overwrite migrated data.

Models and connections

Configure Planning and Image generation separately in settings. New installs default to Codex CLI connections; the plugin does not start model calls or install a CLI on enable. Model discovery runs only when requested. Presets are endpoint suggestions, not proof of account access. Remote endpoints require HTTPS; loopback HTTP is allowed for local services.

Privacy

  • The plugin is MIT licensed, with no payment gate, ads, author-operated service, or client-side telemetry. AI usage is billed by the provider you configure.
  • Only explicit requests send article text, prompts, or reference images to the chosen planning or image service. The vault is not scanned in the background.
  • Accounts and network use: AI generation requires an authenticated Codex CLI or access to your configured AI provider; account access and usage costs depend on that provider. Explicit generation requests send article text, prompts, or selected reference images to that service. WeChat and X publishing require the corresponding platform account and developer credentials, and send the selected content and images to that platform. Optional proxies and SSH relays connect only to servers you configure. Browser-based draft delivery uploads the article snapshot and images to your paired publishing relay and browser. There is no author-operated backend.
  • Files outside the vault: the optional Codex integration finds and starts your local CLI, uses an operating-system temporary job directory, and reads generated images only from that job directory or ~/.codex/generated_images. The CLI uses its own existing sign-in. Local reference images are read only when selected; an optional SSH private-key file is read only from the path you configure.
  • Session data lives in <vault>/.obsidian/plugins/banana-studio/data.json; generated PNGs stay in the configured vault folder. Syncing those locations may sync private content.
  • This is an independent community plugin, not an official Obsidian, Qiaomu, OpenAI, or Dan Koe product.

Development

Requires Node.js 20+ and npm.

npm ci
npm run check

npm run build creates an unminified CommonJS main.js in the project root. The plugin files are main.js, manifest.json, and styles.css.

Banana Studio starts from Banana Design 0.12.1; its first independent release is 0.12.2. Release tags must match the manifest version (no v prefix). Pushing a stable version tag runs the release workflow, which checks version metadata, builds and tests the plugin, then publishes those three files as individual GitHub Release assets.

Project decisions are tracked in the issue tracker and in the release notes.

License

MIT. Based on Banana Design by Treydong. Adapted Codex bridge and provider preset portions come from Qiaomu Design by Xiangyang Qiaomu (joeseesun); see THIRD_PARTY_NOTICES.md.