Login

u/hancengiz

fabriqa spec-driven workflows is out.
▲ 1 r/fabriqaai

fabriqa spec-driven workflows is out.

Ladies and gentlemen, the world's best specification-driven Agentic Development Environment (ADE) has a new feature out. Spec Workflows.

The alpha version of our specs workflows is now available—check it out! I am actively working on enhancing the experience.

Please be aware that agent definitions and workflows are currently in alpha. Expect updates every other day for the next two weeks. I encourage you to use, test, and provide your feedback. Your feedback is appreciated.

https://preview.redd.it/uszp2aebyy0h1.png?width=3095&format=png&auto=webp&s=48cc02244dcfe86d8ed0599e01c2d067acd52505

reddit.com
u/hancengiz — 6 hours ago
▲ 1 r/fabriqaai

running Qwen3.6-35B-A3B-4bit-DWQ locally on my m4 macbook pro.

running Qwen3.6-35B-A3B-4bit-DWQ locally on my m4 macbook pro.

fabriqa.ai LLM agent loop is quite new, still lots to do, but I think I will be using it to execute well-defined specs with a locally hosted Qwen3.6 model. Not bad at all.

https://reddit.com/link/1takftf/video/94f9cd7pgl0h1/player

https://preview.redd.it/0yf2oyvpgl0h1.png?width=1364&format=png&auto=webp&s=2d7c33d70f134d64e711a38fe963b35044d2f813

reddit.com
u/hancengiz — 2 days ago
▲ 1 r/fabriqaai

Fabriqa Macropads are ready. Who would use one, want one?

DM me on twitter or on reddit if you can help /r/fabriqaai reach more developers. I will send you one.

Ignore specs.md sticker for now it will be branded fabriqa.

u/hancengiz — 14 days ago
▲ 1 r/fabriqaai

https://preview.redd.it/kw5bng5omtvg1.png?width=3680&format=png&auto=webp&s=0ab49f11ef6e4840ef542d323b79b0469cc9ade3

In the updated interface, users with a wide screen can now engage in multiple chats side by side. Specifically, within the specifications workflow, you can open the Inception (business analyst) and Construction (developer) agents simultaneously. Each agent has its own terminal, git changes, and all other relevant panels.

Previously, I scoped these chats to the active worktree path, but I have now decided to use a chat container. This change allows the planner agent within the specifications workflow to display artifacts next to it. You can maximize certain panels, collapse or expand them, or rearrange items within the chat container.

If you choose to use a single chat window, the user experience remains unchanged from before.

One significant change is the removal of the tab bar list, which was cluttering the user interface. The left sidebar now shows active chats and indicates which ones are currently running or have completed their turn. Additionally, you can sort the chat list by activity date, ensuring that the most recent chats are always at the top.

Initially, I considered limiting the layout to just two chats side by side. However, seeing Claude’s code support for four splits has prompted me to rethink this.

Would you prefer the layout to feature four chats arranged in two rows and two columns, or would it make more sense to have four rows, particularly for ultra-wide screens? Please avoid suggesting a Miro-like endless canvas, as that might tempt me! :)

reddit.com
u/hancengiz — 26 days ago
▲ 1 r/fabriqaai

TL;DR

Fabriqa uses the public ACP registry for Claude ACP, so new model support flows through this path:

Anthropic SDK release -> claude-agent-acp package release -> ACP registry update -> Fabriqa refresh

The ACP registry update job runs hourly.

In Fabriqa, users can manually trigger a refresh by clicking Check ACP updates in the Agent Providers settings.

If a new model like Opus 4.7 still is not showing up, Fabriqa gives you a flexible workaround: open Claude Agent -> Environment and set:

ANTHROPIC_MODEL=claude-opus-4-7

You can also pin or roll back to other versions, for example:

ANTHROPIC_MODEL=claude-opus-4-6

https://preview.redd.it/04b0xomhqqvg1.png?width=3094&format=png&auto=webp&s=54f4cd67b932068108c47642e1b8d84f69d71ba5

Longer explanation

A few users asked why Claude Opus 4.7 was not immediately visible in Fabriqa through the Claude ACP integration, so here’s the transparent version.

Fabriqa does not silently ship its own patched Claude ACP fork. I use the public ACP registry, which points to a published claude-agent-acp package version. That means model updates usually land quickly, but they still have to move through a real release pipeline:

  1. Anthropic releases support in the Claude Agent SDK
  2. claude-agent-acp updates to that SDK and publishes a new npm package
  3. the public ACP registry picks up that new package
  4. Fabriqa refreshes from the registry

For Opus 4.7, the verified timeline was roughly:

That means the machine-verifiable delay was about:

  • 39m from SDK publish -> Claude ACP support commit
  • 57m from Claude ACP publish -> registry update
  • 1h42m from SDK publish -> registry availability

The registry updater itself runs hourly, not instantly: https://github.com/agentclientprotocol/registry/blob/main/.github/workflows/update-versions.yml

In Fabriqa, users do not need to wait passively. You can go to Settings -> Providers -> Agent Providers and click Check ACP updates to refresh what Fabriqa sees from the registry.

One important clarification: there is currently no public claude-agent-acp@0.29.1 release, so the registry did not “miss” a 0.29.1 update. The latest public Claude ACP package it could pick up is still 0.29.0.

In my case, I was already running 0.29.0 in Fabriqa, but Opus 4.7 still did not show up in the picker until I manually set:

ANTHROPIC_MODEL=claude-opus-4-7

That suggests the issue was likely stale session/model metadata or picker state, not necessarily a bad 0.29.0 release.

This is also where Fabriqa’s flexibility matters. Even if a new model is not yet showing up the way you expect, Fabriqa lets you override the Claude agent environment directly.

If you want the newest model immediately:

ANTHROPIC_MODEL=claude-opus-4-7

If you want to pin or roll back:

ANTHROPIC_MODEL=claude-opus-4-6

So the honest summary is:

  • Fabriqa is transparent about relying on the public ACP registry
  • registry updates are automatic, but hourly, not instant
  • users can manually click Check ACP updates
  • upstream repo commits do not matter until there is a published package release
  • if you still do not see the model you want, Fabriqa gives you the flexibility to override environment variables directly

That flexibility is important for me. I want Fabriqa users to benefit from the ACP ecosystem while still having enough control to move fast when upstream releases, registries, or model pickers lag a little.

If you want an even tighter plain-text version with no code blocks and no bullets, I can give you that too.

reddit.com
u/hancengiz — 27 days ago
▲ 1 r/fabriqaai

Context Aware Recent Files

When working in multiple chats, Fabriqa tracks context and recent file changes. Pressing CMD+P lets you quickly access relevant recent files—those modified or created in your active chat—making it easy to find your spec or changed code files. Fabriqa has many features that simplify your work!

I am focusing on features rather than documentation, so please download Fabriqa and explore its many amazing convenience features.

https://reddit.com/link/1snx1dh/video/7mbn0fho8qvg1/player

reddit.com
u/hancengiz — 27 days ago