Common Workflows

These workflows combine multiple taiku features into end-to-end patterns.

Pair debugging a production issue

You have a production bug and need a colleague to look at your terminal in real time. They should be able to see what you are doing, and you may want to let them type commands too.

Step 1: Start a session.

taiku --name "prod-debug-api-timeout"

taiku opens your desktop app (or browser) and copies the session URL to your clipboard.

Step 2: Share the URL with your colleague.

Step 3: You both see the same terminal. Your colleague can watch as you run diagnostic commands. If they need to type (to run a command in a different shell), you can split the workspace (Ctrl+Shift+H to split horizontally) and they type in the new pane.

Step 4: Use the clipboard to share key outputs. When you copy a stack trace, it automatically appears in your colleague's global clipboard.

Step 5: If this is sensitive and you want your colleague to only watch, use read-only mode:

taiku --enable-readers --name "prod-debug-api-timeout"

Share the reader URL with your colleague. They can see everything but cannot type.

Full-stack development with tunnel previews

You are developing a web application with a frontend dev server and a backend API. You want a collaborator to see both your terminal and a live preview of the app.

Step 1: Start taiku with tunnels for both servers.

taiku --tunnel 5173,3000 --name "fullstack-dev"

Step 2: In the session, start your dev servers in the terminal. Split the workspace so you have one pane for the frontend server and one for the API:

• Ctrl+Shift+V to split vertically
• Run npm run dev in the left pane (frontend on port 5173)
• Run npm run api in the right pane (backend on port 3000)

Step 3: Open the tunnel preview from the workspace UI and tile the frontend alongside your terminals. Now you have three panes: two terminals and a live web preview.

Step 4: Share the session URL. Your collaborator sees the same tiled layout -- terminals and preview side by side. When you make code changes, the preview hot-reloads for both of you.

If you want to skip the approval step for tunnel requests:

taiku --tunnel 5173,3000 --open-tunnel --name "fullstack-dev"

Teaching or onboarding walkthrough

You are onboarding a new team member and want to walk them through the codebase and local development setup. They should be able to watch and ask questions, and occasionally take control to try things themselves.

Step 1: Start a session with a descriptive name.

taiku --name "onboarding: local dev setup"

Step 2: Share the URL. Your new team member joins in their browser.

Step 3: Walk through the setup. They see your terminal output, your active panels, and the same shared session state.

Step 4: When they want to try something, they can request adoption of your terminal. You get a prompt and approve the transfer. Now they own the shell and can type. When they are done, you request it back.

Step 5: Record the session for future reference.

• Open the command palette (Cmd+K or Ctrl+K)
• Select "Start Window Recording"
• Walk through the setup
• Stop the recording when done

You can rename the recording to "onboarding-local-dev-setup" afterward.

Monitoring AI agent sessions

You have multiple AI coding agents (Claude Code, Codex) running in parallel on different tasks. You want to monitor their progress from one place.

Step 1: Start a sandboxed session for each agent.

# Terminal 1
taiku --sandbox ./project-a --sandbox-bridge-claude-auth --name "agent: project-a"

# Terminal 2
taiku --sandbox ./project-b --sandbox-bridge-claude-auth --name "agent: project-b"

Step 2: In each session, start the agent in the terminal. taiku automatically detects the agent and shows status badges on the terminal tile.

Step 3: Install the Agent Monitor plugin for a dedicated monitoring panel. It shows agent status, cost tracking, and session history across all agent terminals.

Step 4: Create multiple workspaces to organize your view:

• Workspace 1: both agent terminals side by side
• Workspace 2: Agent Monitor plugin panel
• Workspace 3: tunnel previews if the agents are running dev servers

Switch between workspaces with Ctrl+Shift+[ and Ctrl+Shift+], or create a new workspace with Ctrl+Shift+\.

Sharing a deployment to stakeholders

You are deploying to production and want stakeholders (PMs, managers) to watch the process without being able to interfere.

Step 1: Start a read-only session.

taiku --enable-readers --name "deploy: v2.4.0 to production"

Step 2: Share the reader URL in your team's Slack channel. Anyone who opens it can watch in real time but cannot type or modify anything. Depending on your viewer-auth setting, they may also need to sign in first.

Step 3: Run your deployment steps. Everyone sees the same output.

Step 4: If something goes wrong and you need a colleague to help, share the writer URL with them privately. They can type in the session while the readers continue watching.

Long-running server process with remote access

You have a process that runs for hours (training, migration, batch job) and you want to be able to check on it from your phone or another machine.

Step 1: Start the session on the server.

taiku --no-app --no-browser --name "migration: users-table-v2"

Step 2: Save the session URL. It is printed to stdout and copied to your clipboard.

Step 3: Start your long-running process in the terminal.

Step 4: From your phone, open the session URL in a mobile browser. taiku's mobile interface gives you a single-tile view of the terminal. You can scroll through output, copy text, and even type commands if needed.

Step 5: If you need to check from a different laptop, just open the same URL. The session is still running as long as the CLI process on the server is alive.

Team standup with shared terminals

Your team does standups where each person shows what they are working on. Instead of screen sharing, you use shared terminals.

Step 1: Each person starts their own session.

taiku --name "standup: alice"

Step 2: Share URLs in the standup channel. Everyone opens each other's sessions in separate browser tabs.

Step 3: When it is your turn, you run commands, show logs, demonstrate features. Everyone sees it in real time.

Step 4: The advantage over screen sharing: viewers can scroll back through terminal history, copy output, and even open a peek view to inspect a specific terminal without disrupting the presenter.