Mefi's Studio AI+
Community

Questions, bugs, ideas and wiki edits all start on GitHub

Mefi's Studio AI+ is a small open-source project. The app's source, releases, issue tracker and docs live in one repository; this site and its wiki live in a second one that anyone can send a pull request to.

Report a bug

Opens the bug template: version, route and builder, steps, and what happened instead.

Suggest a feature

Describe what you are trying to do and what gets in the way today.

Browse issues

Search before posting; someone may already be on it.

Releases

Every portable build with its SHA-256 digest. Watch the repository to hear about new ones.

Changelog

What each release changed, and what is waiting under Unreleased.

Architecture & glossary

The full feature walkthrough in Studio's own vocabulary.

Contributing guide

The check gates, the two test trees and the repository hygiene rules.

This site's repository

Every wiki page is a markdown file. Fix a page or add one with a pull request.
Security

Found a security problem? Report it privately.

Please do not open a public issue for anything that could expose keys, project files or the machine Studio runs on. The security policy explains how to reach the maintainer privately and what to include.

Read the security policy

  • Include the Studio version from App updates, whether you run the portable build or from source, and steps to reproduce.
  • Expect an acknowledgement within a week. Fixes ship as a normal release, and the changelog credits the reporter unless asked otherwise.
Before you post

What makes a bug report useful

Studio has many moving parts: a provider route, a builder CLI, the service loop and your project. A report that names each one gets fixed faster. The bug template asks for exactly this.

  • Version and install kind. The version in Settings › App updates, and portable or source.
  • Route and builder. Which assistant route and builder CLI were selected, and what the readiness line said.
  • Steps and outcome. What you did, what you expected, what happened instead. Task state names help: Ready, Working, Awaiting verification, Needs attention.
  • Evidence. Lines from the studio log (Settings › Log) or the task's activity. Screenshots are fine if they show no private paths.
  • Never paste API keys, settings.json, auth.json, or anything from your data/ folder.

Open a bug report

Help with the wiki

Every page is a markdown file

The wiki is plain markdown under wiki/pages/ in this site's repository, rendered in the browser. Each page ends with an Edit this page on GitHub link that opens the file in GitHub's editor and turns your change into a pull request.

How the wiki is organised and how to add a page →

Good wiki pages

  • Describe what Studio does today. When unsure, check the architecture doc and the changelog.
  • Use the names Studio shows on screen: Give a task, Verify first, Live work, Awaiting verification.
  • Say whether something is in the latest release or only in source.
  • Keep provider prices and quotas out; they change faster than docs do.
Contribute code

Three gates, two test trees

Every application change must pass npm run check, npm test and npm run audit. Iterate with npm run test:fast and npm run lint, rebuild the booklet after renderer edits, and describe the change with the pull-request template.

The full conventions in the wiki →

npm run test:fast       # Node suites without Electron, about 20 s
npm run lint            # eslint, check-only
npm run check           # syntax, targets, spec collisions, CSS gates
npm test                # the gate: Node + Electron fixtures + Python
npm run audit           # renderer/template contracts
npm run build-booklet   # after editing renderer sources
House rules

Short, because this is a small place

Be kind and specificAssume good faith. Say what you saw, not who is to blame.
Stay on topicProvider pricing debates and model wars belong elsewhere; how Studio uses them belongs here.
No secrets, everNo keys, tokens, settings files or private paths in issues, pull requests or screenshots.
Respect the maintainer's timeOne issue per problem, with the details above. Check the changelog before asking for something.