Outworked – Claude Code Agents를 위한 오픈 소스 Office UI
hackernews
|
|
📦 오픈소스
#ai 딜
#ai 에이전트
#claude
#데스크톱 앱
#오픈소스
#코드 생성
원문 출처: hackernews · Genesis Park에서 요약 및 분석
요약
Outworked는 AI 에이전트를 8비트 픽셀 아트 사무실 공간에서 시각적으로 관리할 수 있는 오픈 소스 애플리케이션입니다. 사용자는 에이전트에게 역할과 성격을 부여하고 목표를 설정하면, 시스템이 이를 세부 작업으로 나누어 각 에이전트에게 자동으로 할당합니다. 또한 Claude Code와 통합하여 터미널 명령어, Git 관리, 파일 편집 등 개발 작업을 수행하며, 위험한 명령어에 대한 사전 승인 및 작업 디렉토리 제한 등 강력한 보안 기능을 제공합니다.
본문
Outworked is a desktop app that turns Claude into a team of AI employees. Hire agents. Give them roles. Watch them write code, interact with the web, send messages, and run scheduled tasks — all from an office on your Mac. Fully customizable — import your own sprites, furniture, backgrounds, and fonts via asset packs. Claude Code with a can-do attitude! Download · What's New · How It Works · Examples · Capabilities · Features · Skills · MCP Servers · Channels & Triggers · Asset Packs v0.4.1 — Pop-out chat windows, fixed asset pack zip import and spaces in directory paths, fixed custom sprite loading. v0.4.0 — Asset packs system: custom sprites, furniture, backgrounds, and fonts. Multi-pack support with fallthrough. Music player now plays user-added tracks. v0.3.1 — Slack channel support, triggers UI, improved MCP server wiring, better channel reliability. v0.3.0 — SQLite storage, iMessage channels, scheduled triggers, skills system, MCP server integration. See the full Version History below. - Hire agents — Give each one a name, role, personality, model, and sprite - Describe a goal — Write what you want in plain English; the orchestrator breaks it into subtasks and routes them to the right agents automatically - Watch them work — Agents walk to their desks, write code, interact with the web, send messages, run scheduled jobs — all visible in the office - Ship it — Just let your agents handle the whole workflow end to end These are real things you can do today: You type one sentence. Here's what happens: - The orchestrator breaks it into subtasks and assigns them across your team - Frontend Dev scaffolds the site, writes the HTML/CSS/JS, and starts a local server - Designer reviews the page in the built-in browser, takes a screenshot, and asks Frontend Dev to tweak the spacing - Frontend Dev makes the fix, then runs tunnel_start to get a public URL - Frontend Dev calls send_message to text the link to your cofounder on iMessage You watched the whole thing happen at the office. You are wowed. Your cofounder gives you more equity. Total prompts from you: 1. - You tell your Ops Agent to set up a daily task - The agent creates a scheduled trigger with a cron expression ( 0 9 * * * ) - Every morning, the agent wakes up, queries the GitHub MCP server for open PRs, writes a summary, and sends it to you via iMessage - You read it on your phone over coffee No scripts to maintain. No GitHub Actions to debug. Just an agent with a schedule. - The orchestrator assigns a Researcher agent to each competitor — all three run in parallel - Each agent uses the built-in browser to navigate the competitor's site, read docs, take screenshots, and extract pricing - A Writer agent collects all three findings, writes a structured comparison doc, and commits it to your repo - The Writer asks if you want it sent to Slack — you approve, and it posts to #product Three agents working simultaneously, finishing in minutes what would take you hours. - Project Manager agent pulls all new issues via the GitHub MCP server - It reads each one, labels by priority and type, assigns to the right team member, and adds a first response comment - For any bug it can reproduce, it assigns a Backend Engineer agent to investigate and open a draft PR with a fix - You get a Slack summary of what was triaged, what's in progress, and what needs your attention Write and ship code — Build features, fix bugs, open PRs, review each other's work, run tests, and deploy — across multiple repos at once. Browse the web — Research docs, scrape pages, fill out forms, take screenshots, and bring findings back to the team via the built-in browser. Send and receive messages — Reply to customers on Slack, text you a summary on iMessage, or monitor a channel and trigger tasks when someone says the magic word. Run on a schedule — Daily standups, weekly reports, hourly health checks, one-off reminders. Set a cron and let an agent handle it while you sleep. Query databases — Connect a PostgreSQL MCP server and let agents run queries, generate reports, or investigate production issues without you writing SQL. Manage projects — Create and triage GitHub issues, update Linear tickets, post status updates to Slack — agents can own the workflow, not just the code. Anything you can plug in — Every MCP server you add gives agents new capabilities. Connect your internal APIs, monitoring dashboards, CMS, or anything with a tool interface. If it exists as an MCP server, your agents can use it. - Pixel Office — A Phaser-powered world where your agents walk, sit at desks, and collaborate in real time - Build a Team — Give each agent a name, role, personality, model, and sprite. Mix Claude Opus for hard problems with Sonnet for fast ones - Auto-Orchestration — Describe a goal; the router breaks it into tasks and assigns them to the right agents - Multi-Agent Collaboration — Agents talk to each other via [ASK:AgentName] and a shared message bus - Full Claude Code Power — Every agent gets fu
Genesis Park 편집팀이 AI를 활용하여 작성한 분석입니다. 원문은 출처 링크를 통해 확인할 수 있습니다.
공유