Okou
Delegate cross-app work in natural language while keeping permissions, approvals, and execution under team control.
- Source repo
- okou-ai/okou
- Stars
- ★ 1.2k
- Last updated
- 4d ago
- License
- NOASSERTION
- Primary language
- TypeScript
- FA score
- 56/100 · Major gaps
At a glance
- Works with
- Universal · cross-platformOpenAI API · Claude API
- You'll need
- Typical use
- A founder starts the day with a brief assembled from Calendar, Linear, Slack, and X, then has investor updates drafted from live metrics.
- Main limitation
- No installation commands, version requirements, architecture guide, or self-hosting runbook are present in the supplied material, making deployment effort impossible to verify.
- Source review
- 56/100 · Major gaps
What does this agent do, and when should you use it?
Okou is a workflow agent for marketing, sales, engineering, and operations teams, accepting job-level requests through chat or Slack instead of requiring step-by-step prompts. It determines the steps, selects connected services, and can run several independent task chats concurrently. A completed run can be saved with its instructions and tools as a workspace-owned workflow, then launched by another member, a schedule, or a trigger. Each member runs shared workflows with their own service permissions, while actions that publish externally or spend money stop as drafts or approval requests. Tasks execute in isolated Firecracker microVMs with logs, metrics, and network visibility; the project also claims self-hosting and multi-provider model selection, although the supplied material does not document deployment commands or infrastructure requirements.
A user assigns a job in chat or Slack, after which Okou works out the steps and calls authorized connected services. Named integrations include GitHub, Gmail, Google Calendar, Google Sheets, Notion, Linear, Sentry, HubSpot, Intercom, Figma, Vercel, Dropbox, Airtable, Meta Ads, X, and Reddit, alongside a claimed catalog of more than 3,000 connectors. Documented examples include reading brand material or operational data, publishing a web page, updating CRM records, grouping Sentry events by root cause, filing issues, and producing reports, decks, release notes, and email drafts. Each job receives its own chat and isolated Firecracker microVM, allowing multiple jobs to run at once. Repeated runs can become workspace workflows invoked from chat or Slack and started by schedules or triggers; outbound and spending actions remain subject to human approval.
- A founder starts the day with a brief assembled from Calendar, Linear, Slack, and X, then has investor updates drafted from live metrics.
- A sales or marketing team researches prospects and creators, writes the findings to a tracker, and drafts personalized outreach based on each prospect's content.
- An engineering team groups Sentry noise by root cause, files scoped issues, and generates release notes from merged pull requests.
- An operations lead produces weekly status reports, onboarding checklists, and meeting digests with owners, then schedules follow-up on approvals and deadlines.
- A cross-functional launch team runs landing-page publication, CRM updates, a newsletter draft, and a metrics deck as separate concurrent tasks.
- A teammate who has validated a recurring process saves it as a workspace workflow so colleagues can run it with their own permissions or automate it with a trigger.
How do you install or deploy this agent?
The supplied material provides no local installation commands, self-hosting procedure, dependency versions, configuration files, environment variables, or startup command, so a reproducible self-hosted installation cannot be given. It only documents the hosted signup page at https://app.okou.ai/sign-up and a Slack installation endpoint at https://www.okou.ai/api/slack/oauth/install?publicBrand=okou. Connected services require appropriate accounts and explicit authorization, but credential formats, OAuth scopes, and Firecracker host requirements are not specified.
How do you use this agent?
Sign up for the hosted service or add Okou to Slack, connect the services required for the job, and grant suitable read or write permission for each tool. Assign the desired outcome conversationally—for example, ask it to build a one-page site using a brand kit in Drive—without prescribing every intermediate step. Review the separate task chats, tool activity, and produced artifacts; approve controlled actions such as sending email or changing an advertising budget only after inspection. For recurring jobs, save the run's instructions and selected tools as a workspace workflow, then let teammates invoke it or attach a schedule or trigger. The material does not document the connector configuration screens, retry controls, or a first invocation for self-hosted deployments.
What are this agent's strengths and limitations?
- Independent task chats can run concurrently, supporting launches that combine web publishing, CRM updates, email drafting, and presentation work.
- Saved workflows preserve both instructions and selected tools as workspace assets, turning an individually discovered process into a reusable team operation.
- A shared workflow executes with each member's own permissions instead of borrowing access from its creator.
- Outbound communication and spending changes stop at human approval points, complemented by per-tool and per-agent read/write controls.
- Every task runs in an isolated Firecracker microVM, with logs, metrics, and network visibility for auditing.
- Anthropic, OpenAI, DeepSeek, Google, and other model providers can be selected per run or per agent, reducing dependence on one model vendor.
- No installation commands, version requirements, architecture guide, or self-hosting runbook are present in the supplied material, making deployment effort impossible to verify.
- The connector list does not define the exact operations, permission scopes, or feature coverage available for each service.
- Firecracker microVMs and network access are central to the execution model, but host compatibility, capacity planning, and operating-system requirements are undocumented.
- Pricing, hosted usage limits, model costs, and possible fees for the claimed 3,000-plus connectors are not disclosed.
- Retry behavior, rollback, checkpoint recovery, and handling of partial connector failures are not documented.
- The practical terms for open-source use and self-hosting cannot be established from the repository metadata because the license is marked NOASSERTION and the referenced LICENSE text was not supplied.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|
| Okou This agent | 56 · Major gaps | ★ 1.2k | 4d ago | TypeScript | OpenAI API · Claude API |
| Skales | 36 · Major gaps | ★ 1.9k | 6d ago | — | ChatGPT · OpenAI API · Claude API |
| Open Cowork | 65 · Some gaps | ★ 2.2k | 9d ago | TypeScript | Claude Code · OpenAI API · Claude API |
| Atom Platform | 59 · Major gaps | ★ 901 | 6d ago | Python | OpenAI API · Claude API |
How does FollowAgents rate this agent?
Why each dimension lost points
The README states per-tool/per-agent read-write grants, execution under each teammate's own permissions, human approval before outbound communication or spending, and run-level logs, metrics, and network visibility. Workflows also use constrained GitHub permissions, commit-pinned actions, isolated deployment tokens, ephemeral permission-restricted secret files, and tests that check secrets are not logged. Deductions apply because the product-level controls are mostly asserted without a complete data-flow map, retention policy, authorization matrix, or approval implementation; scheduled cleanup performs real deletion and does not default to dry-run; npm auditing is disabled; and rollback is only indirectly evidenced by a referenced playbook rather than a documented user recovery path. Attribution is weakened by vm0 repository, badge, and advisory links conflicting with the Okou object and licensed-work name.
The supplied tests cover transient SSH retry, ordinary remote failure, consecutive deployment-readiness probes, wrong AWS identity, access denial, OIDC-origin validation, configuration drift, and delivered-evidence checks, with specific failure messages. Dependencies include commit-pinned actions, an exact boto3 version, and frozen-lockfile installation. Deductions apply because the root package test command intentionally fails, its description and author are empty, vm0 and Okou naming is inconsistent, and no installation path demonstrates that ordinary users can obtain all required dependencies.
The README supplies detailed scenarios for founders, sales and marketing, engineering, operations, and support, and describes chat, Slack, schedules, triggers, multiple model providers, and many connectors. This thoroughly establishes audiences and scenarios. Deductions apply because capability boundaries are mostly limited to sending/spending approval and permissions, without unsupported-task, connector-specific, or autonomy-failure boundaries; trigger mechanisms lack exact syntax and conflict rules; and self-hosting requirements, platform compatibility, and configuration steps are absent.
The README has clear sections for value, workflow lifecycle, security controls, role-based scenarios, integrations, contribution, and licensing, with numerous examples. SECURITY.md provides supported-version policy, a reporting channel, response targets, and a maintenance process. Deductions apply because installation and local configuration notes are absent, there is no FAQ, and known limitations are largely licensing or security-scope statements rather than product limitations. Naming shifts between Okou and vm0, while the README's “Open source” statement conflicts with the Business Source License's explicit non-open-source notice and package.json declares ISC. The license text itself is complete, but these conflicts prevent full credit. No substantive changelog or clear release history is supplied.
Illustrated outputs include published pages, unsent email drafts, CRM updates, briefs, tickets, and release notes that would be usable in team workflows. Saved reusable workflows, concurrent tasks, and cross-tool execution offer clear marginal value beyond one-off chat. Deductions apply because most outcomes are promotional examples without static output artifacts, quality criteria, or failure cases; beyond “get started free” and model choice, infrastructure, connector, model-usage, approval-overhead, and self-hosting costs are not explained.
Several security and deployment claims trace to concrete workflow assertions and tests, including token isolation, keeping secrets off command lines, stopping on wrong identity, excluding sensitive values from reports, readiness probes, and delivery verification. README, SECURITY.md, workflows, and tests provide partial cross-source support. Deductions apply because major claims such as a Firecracker microVM for every task, 3,000+ connectors, credentials never leaving the sandbox, and full auditability lack direct implementation evidence in the supplied files. Promotional facts, illustrative scenarios, and inferences are not clearly separated, and external badges cannot provide independent verification in this static review.
- License metadata conflicts: LICENSE uses a restricted Business Source License 1.1, package.json declares ISC, and the README calls the repository open source. Verify licensing before adoption, redistribution, or production use.
- Do not assume from the README alone that every external action waits for approval. Verify deployed approval policies, triggers, and schedules, especially the Clerk test-resource cleanup job, which defaults to performing actual deletions.
- Confirm the relationship among Okou, vm0, the linked CI badges, security advisories, and the responsible maintainer before relying on update or vulnerability-response channels.
- Before using real credentials or business data, establish data destinations, log and artifact retention, connector scopes, network-egress controls, and credential lifecycle; the supplied material does not document these comprehensively.
- This static review did not execute code or tests and did not verify the Firecracker isolation, connector-count, production-approval, or full-auditability claims.