What is Slate Terminal?
Slate Terminal is a native terminal for macOS that lets developers shape their workspace around the work they do. Alongside shell panes, users can add custom panels, commands and layouts, or ask an agent to create them. Slate provides the workspace while users choose which agent and model to use. It runs on Apple silicon and requires macOS 27 or later, and is actively in development.
Slate Terminal Features:
Nested Pane Layouts: Work across tabs and nested splits in a native Mac workspace, with options to zoom a pane or make panes even.
Custom Workspace Panels: Create views with HTML, CSS and JavaScript to put dashboards, review queues or scratchpads alongside a shell.
Plugin Components: Plugins can add panels, commands, header buttons, background services and responses to workspace events.
Agent CLI: The slate-term CLI lets an agent write plugins, split panes, send input, capture the screen and save layouts.
Agent Activity: A floating pill indicates which agent is working in a pane and what it is working on.
Saved Workspaces: Save a layout from the command picker as a named app with an icon, then open it from Spotlight or the Dock.
Slate Terminal Benefits:
Less Context Switching: Keeping project-specific views beside the shell can reduce the need to move between separate windows while working.
Work That Fits: Custom panels and layouts let developers arrange a workspace around their own scripts, reviews or monitoring needs.
Clearer Agent Work: Seeing agent activity by pane can make it easier to spot work that needs attention and decide where to review it.
Repeatable Setups: Saving a layout as an app makes a useful workspace easier to reopen when returning to a task.
Flexible Agent Choice: Choosing an agent and model separately from the workspace lets users keep using the agents they already work with.
Use Cases:
Review Agent Changes: Build a review workspace with an agents sidebar and a queue for checking changes before merging them.
Track a Deployment: Put deployment status, latency and a live site beside the shell when following a rollout.
Monitor Experiments: Create an experiment workbench that keeps training activity, runs and loss curves together.
Run a Script: Make a small interface for a script, with inputs, a Run button and a place to see its results.
Organize Pull Requests: Build a board for pull request reviews and CI checks alongside the branch being worked on.

