GwenSign in

Docs

What Gwen can do

Ask Gwen for an outcome across work and life. Gwen scopes the job, uses the engines and rails it needs, builds missing paths, and turns repeated work into reusable capability.

Ask for the outcome

The simplest way to understand what Gwen can do is to stop thinking in features and start thinking in outcomes. You do not pick a module; you state what you want to be true, and Gwen works out how.

That covers business, creative, technical, operational, and personal work — software, content, websites, CRM, email, research, finance, support, hiring, and the workflows that connect them. The list below is illustrative, not a menu: the real answer is "ask for the result you want."

Build and launch

Gwen can create real, working artifacts and keep improving them:

  • Websites, landing pages, and marketing sites.
  • App-like workspaces, client portals, and internal tools.
  • Forms and lead capture wired into your workspace.
  • Ongoing edits, new sections, and content after launch.

Builds run on real coding engines in a real runtime, with independent quality checks before you see them.

Grow and sell

Gwen can run the growth loop end to end, with delivery on rails you control:

  • Capture leads from your site into a lightweight CRM.
  • Keep contact, company, source, consent, and activity records.
  • Draft newsletters, social posts, replies, images, and campaigns.
  • Prepare nurture and follow-up sequences for approval.

Creation and intelligence are built in; sending happens through your connected accounts or your own export.

Research and decide

Gwen can do the reading and synthesis that decisions depend on:

  • Competitor, market, and customer research.
  • Summaries and briefs from documents and the web.
  • Comparisons, analyses, and decision support with sources.
  • Monitoring of topics that matter to your work.

Research produces reviewable artifacts with their reasoning attached, not just a confident paragraph.

Software and technical work

Gwen can take on real engineering work, gated by approval where it touches live systems:

  • Scope and plan changes to a codebase.
  • Write and edit code, run builds, and run tests.
  • Prepare diffs and pull requests for review.
  • Coordinate a GitHub repository as a durable project.

Repository pushes and deploys require approval and the right connected workspace.

Operations, inbox, and the everyday

Gwen can absorb the recurring work that eats a week:

  • Triage an inbox and draft replies for approval.
  • Organize information, documents, and records.
  • Turn repeated requests into reusable workflows.
  • Keep track of priorities, people, and decisions.

This is where Personal Intelligence and Enterprise Intelligence overlap most — the small things that compound.

Gwen creates or connects the path

If a path for your request already exists, Gwen uses it. If a job needs something that is not there yet — a tool, a file, a runtime, an integration, a domain, an approval, a budget, or a brand-new workflow — Gwen scopes that and either builds it or asks you for it.

This is why "what can Gwen do" does not reduce to a fixed feature list. Gwen is built to assemble the path to an outcome, not just to run pre-wired buttons.

Gwen uses the stack underneath

To deliver these outcomes, Gwen draws on model routing across hundreds of models from providers including Anthropic, DeepSeek, Google, Groq, Moonshot, and OpenAI via Tokaroo, code workspaces, browsers, memory, document handling, media generation, hosting rails, business-system integrations, approval gates, telemetry, and reusable skills.

You never operate these directly. Gwen selects and coordinates them so you stay in the language of outcomes while the machinery does the work.

The work becomes reusable

Whatever Gwen does once, it can do better the next time. Repeated requirements turn into memory, knowledge, workflows, skills, and playbooks through a governed learning loop.

So capability is not static. The set of things Gwen can do well for your workspace grows as you use it — and proven patterns can graduate into shared playbooks available across Gwen.

Approval protects real-world action

Breadth of capability is paired with control. External sends, publishing, spend, deployments, destructive changes, sensitive data changes, and account actions ask for approval or follow a policy you configure.

So "Gwen can do almost anything you can describe" is true — and bounded by the fact that the consequential, outside-world parts always run with your consent. See Approvals, control, and your data.

Gwen

Public work intake

Hi, I'm Gwen. What do you want to do?

Enter sends. Shift+Enter adds a line.
Online
Preview
Ready
Replies: Web