Triggered from Linear
Mention an agent on the issue and Quester routes the job immediately, without inventing a parallel workflow your team has to maintain.
@mention an agent on any Linear issue. Quester orchestrates the work across your workstations — planning, building, reviewing, and shipping — all visible in a live dashboard.
Team collaboration
Without Quester Cloud
With Quester Cloud
Every agent run is visible to the whole team, not just the person whose machine executed it.
See which machines are connected, how many runs each is handling, and whether any are offline.
Teammates connect their own machines; work is dispatched to whoever is available.
The whole team can see what an agent is doing in real time from the shared dashboard.
If one machine goes offline, runs are dispatched to other connected workstations.
Mention an agent in Linear. Quester routes the work, your machines execute it, and the dashboard shows every step. No context switching, no new tools to learn.
Mention an agent on the issue and Quester routes the job immediately, without inventing a parallel workflow your team has to maintain.
Execution stays on developer workstations. Code, credentials, and secrets remain inside your own environment while the server coordinates the flow.
Live streams show active agents, workstation health, deferred runs, and completion state so everyone can see what the warband is doing.
Peon builds, Grunt reviews, Headhunter tests, Shaman plans. The system is structured around operational jobs, not a single generic bot.
Quester sits between Linear and your workstations. Webhooks flow in, agents spin up, code stays on your machines. Think CI for AI-powered engineering.
Developer machines or dedicated build boxes. You choose what connects.
The orchestrator routes work and tracks state. It never clones repos or stores source code.
Workstations connect to the orchestrator — no inbound ports, no VPN required.
Every agent run triggered from Linear — visible across your whole team. Live activity, cost tracking, and run history in one place.
Stream agent output in real time as it happens.
Every past run with status, duration, and agent.
| Issue | Agent | Status | Duration | Cost |
|---|---|---|---|---|
| SK-389 | @peon | running | 2m 14s | $0.18 |
| SK-371 | @grunt | done | 4m 02s | $0.31 |
| SK-368 | @headhunter | done | 1m 55s | $0.12 |
| SK-362 | @peon | done | 6m 41s | $0.49 |
Connected machines and active run counts at a glance.
Token spend and cost per run across every agent.
| Issue | Agent | Status | Duration | Cost |
|---|---|---|---|---|
| SK-389 | @peon | running | 2m 14s | $0.18 |
| SK-371 | @grunt | done | 4m 02s | $0.31 |
| SK-368 | @headhunter | done | 1m 55s | $0.12 |
| SK-362 | @peon | done | 6m 41s | $0.49 |
Stream agent output in real time as it happens.
Every past run with status, duration, and agent.
Connected machines and active run counts at a glance.
Token spend and cost per run across every agent.
Quester runs on your own infrastructure. Pick your install method below.
# Clone the repo
git clone https://github.com/simontzky/quester.git
cd quester
# Configure your credentials
cp .env.example .env
# Edit .env with your Linear OAuth + GitHub App credentials
# Start everything
docker compose up# Prerequisites: Elixir 1.19+, Erlang/OTP 28+, Node.js 22+
git clone https://github.com/simontzky/quester.git
cd quester/server
# Install dependencies
mix deps.get
# Configure credentials
cp .env.example .env
# Start the server
mix phx.serverEverything you need to deploy, configure, and extend Quester.
Install Quester and ship your first issue in minutes. Setup guide, config, and first run.
How the server, agents, dashboard, and worker fit together. Data flow and component map.
What each bot does — peon writes code, grunt reviews, headhunter runs QA, shaman plans.
Config files, secrets, OAuth tokens, and environment variables explained.
Monitor agents, active quests, run history, and workstation health in real time.
Quester is a real system with real moving parts: orchestrator, dashboard, CLI, worker, and workstation execution. The repository shows how the pieces fit together.
Repository
simontzky/quester
The Linear companion that turns issues into shipped pull requests through agentic orchestration.
Stack map
Phoenix orchestration, webhooks, sessions, follow-up chains, and dashboard API.
The same visual system you see here, used for live agent and workstation monitoring.
A direct operator surface for booting the server, workstations, and local workflows.
Durable webhook buffering so events survive internet or tunnel instability.
Pricing
Full agentic engineering pipeline, open source. Cloud saves setup time.
Self-hosted. Full control. No account needed.
Your workstations, our orchestrator.
Dedicated infrastructure and white-glove onboarding.
We're building the bridge between your Linear workspace and autonomous engineering agents. Self-hosted first, managed cloud next.
The operational core lands first: server, workstations, dashboard, and the full agent pipeline running on your own machines.
Then comes hosted onboarding, team visibility, and the smoother cloud path for teams that want Quester without running the infra.
Get notified when access opens