Skip to content

Add atomic-chat BYOK Marketplace Plugin #1108

@yanalialiuk

Description

@yanalialiuk

What

Proposal to add an atomic-chat marketplace plugin that gives Droid users a validated, reproducible setup flow for connecting to Atomic Chat as a BYOK backend using Factory’s existing generic-chat-completion-api integration.

Atomic Chat is an Apache-2.0 local-first desktop application exposing a single OpenAI Chat Completions–compatible HTTP API across local and configured cloud models.

The integration uses the documented local API base URL:

http://localhost:1337/v1


Why

Users can already configure this manually, but we repeatedly see the same setup failures:

  • incorrect localhost port
  • invalid API path
  • wrong model identifier
  • local API server not running
  • auth/config mismatch

The goal of the plugin is to provide engineering-focused setup guidance as a reusable skill — not promotional content.

Atomic Chat intentionally exposes a standard OpenAI-compatible interface, so the integration surface is minimal and aligns naturally with Droid’s existing BYOK/custom gateway model.

This is especially useful for local-first and privacy-sensitive workflows.


What’s included (planned PR)

Path Purpose
plugins/atomic-chat/.factory-plugin/plugin.json Plugin manifest (author: Atomic Chat, license: Apache-2.0)
plugins/atomic-chat/skills/atomic-chat-byok/SKILL.md Step-by-step BYOK setup, JSON examples, verification, troubleshooting
plugins/atomic-chat/README.md Short operator-facing overview
skills/atomic-chat-byok Symlink → ../plugins/atomic-chat/skills/atomic-chat-byok (required by CI skill exposure rules)
.factory-plugin/marketplace.json Register plugin (proposed category: productivity, unless maintainers prefer another)
README.md Add plugin entry under “Available Plugins”

Optional v1

A lightweight slash command only if maintainers think it provides meaningful workflow value beyond the skill itself.


Out of scope

  • changing Droid runtime behavior
  • introducing custom protocols
  • proxying Factory-managed providers
  • modifying Factory APIs
  • promotional or marketing-oriented content

Install (post-merge)

droid plugin marketplace add https://github.com/Factory-AI/factory-plugins
droid plugin install atomic-chat@factory-plugins


Invocation

  • model selection / smoke-test guidance
  • skill-driven setup when users ask to connect Droid to Atomic Chat
  • local OpenAI-compatible BYOK configuration help

Questions

  1. Is this category of OpenAI-compatible local-provider integration appropriate for the official marketplace?

  2. Any naming constraints for plugin or skill IDs?

  3. Preferred contribution flow:

    • issue discussion first
    • or draft PR immediately after initial approval?

Maintenance

We’ll maintain the plugin documentation as Atomic Chat’s local API evolves and will keep CI requirements (including skill exposure symlink rules) up to date.

Thanks!

— Atomic Chat
https://github.com/AtomicBot-ai/Atomic-Chat

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions