From Beamt · In Development
Your autonomous AI company.
Quarksmith is not a task runner — it’s a company of AI agents with distinct roles, shared memory, and a local coordination bus. Engineers, planners, and curators work toward your goal day and night. In development — join the early access list below.
You’re on the list. We’ll be in touch.
Something went wrong. Please try again or email hello@beamt.io.
Quarksmith gives you a company of AI agents. You write a goal — build a billing portal, maintain your API’s security posture, run customer support for your SaaS — and a swarm of agents with distinct roles works toward it, day and night.
Each agent has a persona and a job. An engineer agent claims cards, writes code, opens MRs, watches CI, and self-heals on failure. A planner agent reads the goal and the board state and refills the backlog when work runs low. A curator agent maintains the hive — a shared, git-backed memory that grows with every commit. They coordinate on a local bus: “auth module done, issue #42 unblocked.”
You get a swarm dashboard: one row per agent, current card, last three actions, weekly spend. When an agent hits something it can’t resolve alone — a design decision, a missing requirement — it escalates to you and the swarm keeps running. You answer the question; it continues.
The Flow
From vision to execution — you stay at the helm.
Describe what you want to build, maintain, or run — a project, product, or service. The swarm reads it and knows what it is working toward.
A planner agent breaks the goal into cards. Engineer agents claim them. A curator tracks what has been learned. Each agent has a persona, memory, and a clear role.
Engineers write code, open MRs, watch CI, and self-heal. The planner refills the backlog as cards complete. Agents coordinate via a local bus. Blocked agents escalate rather than spin.
One row per agent: current card, last actions, status, spend. The work happens while you’re away; the dashboard shows what changed.
Differentiation
A company of agents is not a bigger task runner. Here’s what changes.
Cursor and Copilot hand you a suggestion. Devin runs a single agent once. Quarksmith instantiates a company: engineers, planners, curators — each with a persona, each with memory, each with a role. They coordinate toward a goal.
Every agent builds and reads from a shared, git-backed memory: facts, decisions, lessons learned — all versioned, searchable, and persistent across weeks of operation. The swarm gets smarter over time.
Agents message each other directly: “auth module done, #42 unblocked.” No orchestrator in the hot path. The swarm self-coordinates so you don’t have to manage the handoffs.
When an agent hits something it can’t resolve — a design decision, a missing requirement — it surfaces the question to you and keeps the swarm moving. You get a question, not a failed run.
Solo founders who want a team they can actually afford to run 24/7. Engineering leads who want the backlog to move while they sleep. Anyone with a vision they’d delegate to a senior engineer if they could.
Quarksmith is not for the developer who wants to be in the editor — Cursor, Copilot, and Claude Code already serve that need. It’s not for the team that wants to hand one task to one agent and review the result — Devin already serves that. Quarksmith is for the person who wants to be at the helm: you set the vision, the agents execute, and you make the calls when something needs a human.
A typical day: you set a goal — “harden the auth layer, ship the new billing page, and close out the open support tickets.” By morning, the planner has decomposed it into twelve cards, engineers have claimed eight, two are in CI, and one has escalated a question about token expiry policy. You answer it in thirty seconds; the agent resumes. That’s the helm.
Architecture
Built by a former MedTech CTO who took HIPAA and HITECH compliance seriously for two decades. That mindset carries over here.
Quarksmith doesn’t run on your servers.
Every task gets a fresh container, deleted on completion.
Quarksmith pulls a clone, pushes branches; never holds your tree.
GitLab and GitHub secrets are never copied into Quarksmith’s environment.
Same architectural pattern used in FDA-audited systems where data exposure has legal consequences.
At launch
Roadmap
Pricing
You pay for the work Quarksmith does — not for seats, not for agent count, not for repo access.
Early-access pricing details ship with the launch. Get on the list to be first.
Quarksmith is built by Greg Smethells, former CTO of Medstrat — an FDA-approved medical imaging platform that served 25%+ of US orthopedic practices and reached $10M ARR before its acquisition by Zimmer Biomet (Fortune 500). Twenty years of writing software that runs in operating rooms and passes FDA audits. Now applying that same discipline to autonomous software engineering.
More about GregCommon questions
Quarksmith runs a company of AI agents toward a goal you describe — building, maintaining, or running a project, product, or service. Each agent has a role and persona: engineers write code and open MRs; a planner decomposes goals into work; a curator maintains the swarm’s shared memory. They coordinate locally, operate day and night, and escalate to you only when they’re genuinely blocked.
Cursor and Copilot are interactive tools that wait for your next keystroke. Quarksmith doesn’t wait. It runs a swarm of agents with roles and memory, working toward a goal you’ve described, whether you’re at your desk or not.
One-shot agents run once, produce output, and stop. Quarksmith’s agents live for weeks. They maintain memory across tasks, coordinate with each other, and keep working until the goal is reached or you tell them to stop.
At launch: an engineer agent writes code, opens MRs, and watches CI; a planner agent breaks goals into cards and refills the backlog; a curator agent maintains the shared hive memory. More personas follow as the platform matures.
On Beamt-hosted infrastructure, in ephemeral Docker containers that are deleted as soon as the task is complete. Quarksmith works from a clone of your repo, never the original tree, and never holds onto secrets — those stay in your CI/CD.
Yes. Quarksmith opens MRs and pushes branches; your CI runs against them as it would for any human-authored MR. If CI fails, the engineer agent reads the logs and pushes a follow-up commit.
Usage-based. You pay for the work Quarksmith does — not for seats, agent count, or repo access. Early-access pricing details ship with the launch.
It escalates. A blocked agent surfaces the question to you through the dashboard, marks its card as awaiting input, and the swarm continues with other work. You answer; the agent resumes.
Drop your email at the top of this page to be first in line.
Get early access