AI Productivity

Custom Agents

Register any coding CLI — a fork, an in-house wrapper, or a tool that shipped last week — as a first-class agent with its own name, colour, logo, resumable sessions and memory files. It then appears in Add Terminal, Change AI, Prompt History, Resume and Memory exactly like the built-in agents, with no 1DevTool release required.

Download 1DevToolAll Features
Custom Agents

More Screenshots

Click any image to zoom in

A custom agent set to Inline transcript with Pi-style sessions auto-detected and two recent sessions previewed before saving
The Sessions panel with resume template {cmd} --session {id}, continue template {cmd} -c, a command-line picker, and AGENTS.md as the project memory file
Resume AI Sessions filtered to a custom agent, listing transcripts with its badge, turn counts and Change AI, View, Copy ID and Resume actions
Two terminal tabs running a registered custom agent, each showing the agent's own monogram logo and CUSTOM label

Why You Need This

How this feature boosts your daily productivity

Finding a coding CLI you like used to be the easy part. Running it in 1DevTool meant a tab labelled with the raw command, no logo to tell it apart, no session history when you quit, no Memory panel because nothing knew which file it read, and no entry in Change AI or Prompt History. The only fix was to request support and wait for a release. Custom agents close that gap: you describe the CLI once — name, colour, where it stores transcripts, how it resumes — and from then on every surface that knows about Claude and Codex knows about yours too.

How It Works

Get started in 4 simple steps

1
1

Mark the command as an AI agent

In Settings → Terminal → Commands, add or edit the command and set Run mode to AI agent — that alone gives it prompts, orchestration and idle detection.

2
2

Expand Agent integration and register it

Tick "Register <name> as a custom agent", then set a display name, an accent colour and an optional logo. Without a logo the first letter sits on the accent colour.

3
3

Point it at its sessions, then press Test

Choose Pi-style sessions, Claude-style projects or a flat JSONL folder and give the path. Test reports what it found — "Found 2 usable sessions from 3 JSONL files" — and previews them before you save. Open reveals the folder.

4
4

Fill in the resume templates once

Give the resume-by-id form ({cmd} --session {id}), the continue-latest form ({cmd} -c) and the agent’s own picker — a slash command typed into the running TUI, or a flag such as {cmd} -r.

5
5

Pick a screen mode and name the memory files

Full-screen TUI lets the agent own the alternate screen and its scrolling; Inline transcript keeps scrollback in 1DevTool the way Claude and Codex do. List the project memory files (e.g. AGENTS.md) and an optional global file.

Without 1DevTool

The manual way vs. the 1DevTool way

The Hard Way

# found a coding CLI you like
# run it in a plain shell
# the tab shows the raw command, no logo
# quit -> the conversation is gone
# Resume, Change AI, Memory: not listed
# file a request and wait for a release

The 1DevTool Way

Settings -> Terminal -> Commands -> AI agent
Register it: name, colour, logo
Point at its sessions, press Test
Resume, Change AI and Memory all work

Key Capabilities

Everything included with Custom Agents

Register any coding CLI as a first-class agent without waiting for a release
Give it a display name, accent colour and a logo downscaled to 64px
See it in Add Terminal, Change AI, Prompt History, Resume and Memory
Scan Pi-style, Claude-style or flat JSONL session folders
Test a session path and preview real conversations before saving
Set resume, continue and picker templates with {cmd} and {id}
Choose Full-screen TUI or Inline transcript scrollback behaviour
Name the project and global memory files the Memory panel edits
Show, hide and reorder custom agents alongside the built-ins

Why It Matters

The productivity impact of having ai productivity built into your workspace

No More Waiting For Support

A fork, an in-house wrapper or a CLI that shipped last week becomes a fully wired agent in about five minutes, instead of a feature request with no ship date.

Your Sessions Survive The Quit

Point 1DevTool at the transcripts the CLI already writes and Resume, continue and the agent’s own picker all start working — with a Test button that proves the path before you save it.

Tell Six Terminals Apart

Its own logo and accent colour follow the agent through every surface, so a busy workspace stays readable without opening tabs to check.

The Built-Ins Stay Protected

Built-in names are reserved, so a custom registration can never shadow Claude or Codex, and deleting the command asks before dropping the registration.

More in AI Productivity

Other features in this category you might find useful

Prompt History

Search prompts and sticky notes from Remote Control while away from the desktop. Switch between This project and All projects, filter prompts by agent or notes by source, copy entries, delete with Operator access, and sync local prompt history.

Resume UI

Browse, search, and resume past AI sessions from Claude Code, Codex, and Gemini CLI — or combine multiple sessions into one.

Combine Sessions

Select sessions from Claude Code, Codex, and Gemini CLI and merge them into a single conversation — giving your next agent the full cross-agent context.

AI Diff Review Panel

Track every file modification any AI agent makes — Claude Code, Codex, Gemini, Amp, custom — and review, accept, or revert their work per file from a dedicated panel with inline diff overlays in the editor.

PreviousAll FeaturesNext

Ready to boost your workflow?

Download 1DevTool for free and experience Custom Agents along with 277 other features — all in one app.

Download for FreeView Changelog