goose

Does it fit your conditions?

You want one extensible workspace and can configure models and extensions.

Setup

Configure tools

Interface

Desktop app, Terminal

Access

Provider API key / Product account

Workspace

Connected apps

Install goose and select a supported provider or account path, then configure relevant extensions.

Reviewed scope: AAIF goose desktop and CLI.

Coding and office fit

Local execution does not mean model requests remain local. Office capabilities depend on extensions.

Costs and context

Provider / supported account / local compute

Compare provider usage and extension costs; open-source software does not imply free inference.

Reduce unnecessary work: Use a small set of task-specific extensions and reusable recipes.

Measured tokens / task

Unknown — not measured

Measured cost / task

Unknown — not measured

Compare the same deliverable and acceptance criteria, including retries and your review time. Local execution does not establish local model processing.

Try one real task

1. Install goose and select a supported provider or account path, then configure relevant extensions.
2. Start with a small task: Edit and verify software using local tools and extensions.
3. Check the result against your original files and acceptance criteria before expanding the workflow.

Before relying on this workflow, check the current plan, device, region, language, file format, and required permissions.

Bring your work with you

Carry recipes, project rules, and output files. Revalidate extension permissions and provider access.

A reviewed brief can carry context. Native history, internal memory, account permissions, and running tasks are not assumed to transfer.