Your development toolchain, next to your agents.
A software team needs a code host with CI, a chat, an issue tracker, error tracking, analytics, LLM traces and logs. The factory picks an open-source app for each job and puts it inside Loams, next to your coding agents in Studio. An issue or an error becomes an agent thread; the thread becomes a pull request. You run the apps; Loams never forks or patches them.
What ships today. In Loams v0.1.0 the factory is experimental and lives in Loams Desktop, under Studio. Its panels only read; nothing in the factory merges or deploys on its own. The loop in which agents take an issue all the way to a reviewed change is being redesigned.
Every app in one window, beside your agents.
Every app, one window
Read-only panels for open pull requests, issues, unresolved errors and recent traces, and each app’s own full UI in an isolated view.
From a signal to a thread
A Plane issue or a GlitchTip error becomes the draft of a Studio thread, where an agent picks it up.
From a thread to a pull request
The thread’s branch becomes a Forgejo pull request, opened by loams-agentd with the factory’s Forgejo credential.
Credentials out of the page
App tokens are encrypted at rest and decrypted only in the desktop’s main process, never in the page.
The desktop holds the keys; the apps stay yours.
Loams Desktop reads each app through an allowlist of read-only calls and opens its full UI in an isolated view. Dashed parts are not built yet.
Real apps, run unmodified.
Each job goes to an existing open-source app, run from its official image. Bring the ones you already use.
- ForgejoCode, pull requests and CI
GPL-3.0-or-later - ZulipTeam chat by topic
Apache-2.0 - PlaneIssues and planning (through ItsAPlan)
AGPL-3.0 - GlitchTipError tracking
MIT - OpenPanelProduct analytics
AGPL-3.0 - MatomoWeb analytics
GPL-3.0-or-later - LangfuseLLM traces and cost
MIT, except ee/ - OpenObserveLogs and traces (full UI only)
AGPL-3.0
Forgejo, Zulip, Plane, GlitchTip, OpenPanel, Matomo, Langfuse and OpenObserve are trademarks of their owners. Loams runs them unmodified and is not affiliated with them.
From a toolchain to a loop.
The factory in the browser
In reviewApp connections move into loams-agentd, so the factory opens in the browser console as well as on the desktop. Still read-only.
The agent loop, redesigned
Being redesignedAn issue or an error becomes a reviewed change, with agents doing the work between the steps and a person approving every merge and deploy. The first plans were retired on 2026-10-19; new ones are coming.
A factory you install
PlannedToday you run the apps yourself. Their images are already pinned by digest in the repository; a package that brings them up for you comes next.
Not built, and not promised on this page: per-app agents, a chat that drives them, budgets and automatic reverts. They were in the first design and will be decided again in the new plans.
Bring your toolchain next to your agents.
Install Loams Desktop, open the Factory group in Studio, and give it the URL and a token for each app you run. Your tokens stay on your machine.