tucan studio

Docs

Guides for working with Tucan Studio, building extensions, and using the registry API.

User guides

Welcome to Tucan Studio

Tucan Studio is an AmigaOS-native IDE built in AmLang. It runs on AmigaOS m68k, MorphOS PPC, AROS, macOS, Linux, and Windows.

AI Agent

Tucan Studio has a chat sidebar that talks to an AI service of your choosing. It is not tied to one vendor: the studio ships clients for OpenAI and Claude (Anthropic), and an extension can add more…

Aminet

Tools -> Aminet opens a browser for aminet.net in the right sidebar: search the archive, read a package's README, and download it without leaving the studio.

Editor & Tabs

Clicking a file in the folder tree opens it in the editor.

Extensions

An extension adds something to the studio: menu entries, an editor for a file type, workspace templates, a bundled tool, or an AI provider.

Git

The Git tab in the left sidebar shows the state of the repositories in the open workspace and performs the everyday operations on them. It drives a real git binary -- it is a front end, not a…

Keyboard Shortcuts

Menu items use the platform's menu modifier: right-Amiga on AmigaOS and MorphOS, Cmd on macOS, Ctrl on Linux and Windows. Below, Mod means whichever of those applies to you.

Settings

Tucan Studio -> Settings opens the settings window. A list of sections runs down the left; the Save button at the bottom writes everything at once. Closing the window without saving leaves the stored…

Terminal (CLI)

The bottom-bar CLI is a real terminal, not a shell emulator. On AmigaOS it runs commands through a custom DOS handler that bridges CON: for stdin (so isatty-checks pass in libnix binaries) and PIPE:…

Workspace commands

The Workspace menu holds commands you define for the open project -- build, clean, run, deploy, whatever the project needs. Picking one opens the Workspace terminal and runs it there.

Workspaces

A workspace in Tucan Studio is just a folder on disk. It becomes the root of the folder tree in the left sidebar; everything the IDE does (Git, extensions, build commands) is scoped to that root.

Developer documentation

Build and publish extensions, and explore integration designs. Design documents describe proposed features.

Registry API

Publish releases, manage accounts, and submit issues through the HTTP API.

API documentation →