원클릭으로 Manus에서 모든 스킬 실행

시작하기

xterm-pty

스타5

포크0

업데이트2026년 3월 3일 23:03

xterm.js 6.0 + portable-pty terminal patterns for agentcockpit

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Rixmerz

Rixmerz/agentcockpit

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

xterm.js + PTY

Overview

agentcockpit uses xterm.js 6.0 for terminal rendering and portable-pty (Rust) for cross-platform PTY management. The PTY runs user's shell, and AI agents are launched as commands within it.

Configuration

xterm.js 6.0 with addons: fit, clipboard, web-links, canvas/WebGL renderers
portable-pty 0.8 (Rust crate)
Terminal: TERM=xterm-256color, 10000 line scrollback
Font: JetBrainsMono Nerd Font, 14px

Data Flow

User types → xterm.onData → usePty.write → ptyWrite IPC → Rust PtyManager.write → PTY master
PTY output → Rust reader thread (4096 byte chunks) → pty-output-{id} event → usePty.onData → xterm.write

Common Patterns

Spawning PTY (Rust)

// PtyManager::spawn creates PTY pair, spawns $SHELL
let pair = pty_system.openpty(PtySize { rows, cols, .. })?;
let mut cmd = CommandBuilder::new(shell);
cmd.cwd(cwd);
cmd.env("TERM", "xterm-256color");
// Clear nested detection vars
cmd.env_remove("CLAUDECODE");
cmd.env_remove("CLAUDE_CODE_ENTRYPOINT");
let child = pair.slave.spawn_command(cmd)?;

Writing to PTY (TypeScript)

import { ptyWrite } from '../services/tauriService';
await ptyWrite(ptyId, data);

UTF-8 Boundary Handling (Rust)

The reader thread buffers incomplete UTF-8 sequences across reads using find_utf8_boundary() to avoid splitting multi-byte characters.

Activity Detection

const { signalOutput, signalUserInput } = useTerminalActivity({
  terminalId,
  threshold: 3000, // ms of silence before "finished"
  onFinished: handleTerminalFinished,
});

Resume UUID Detection

// In TerminalView onData callback
const stripped = data.replace(/\x1b\[[0-9;]*[a-zA-Z]/g, ''); // Strip ANSI
resumeBufferRef.current += stripped;
const match = resumeBufferRef.current.match(
  /claude\s+--resume\s+([0-9a-f]{8}-[0-9a-f]{4}-...-[0-9a-f]{12})/
);
if (match) sessionEvents.emit('resume-detected', { uuid: match[1], terminalId });

Best Practices

Never block PTY writes — send input immediately, do async work (snapshots) after
Buffer incomplete UTF-8 in reader thread — don't emit partial sequences
SIGTERM then SIGKILL on close — give process group time to clean up
Guard 0x0 resize — happens when xterm container gets display:none
Use refs for listeners — prevent re-renders from killing event subscriptions

이 저장소의 다른 Skills

같은 저장소

testing

Rixmerz/agentcockpit

Testing strategy, patterns, and coverage optimization for quality assurance. Use this skill whenever the task involves deciding what to test, how to structure tests, what coverage to aim for, when to use mocks vs real dependencies, or how to write tests that actually catch bugs (not just pass). Also use when the user asks about test pyramids, flaky tests, integration vs unit, TDD, or improving an existing test suite.

2026-04-105

validation

Rixmerz/agentcockpit

Production readiness validation — runs all checks before merging or deploying. Use this skill whenever the task involves verifying that code is ready to ship: type checking, linting, tests passing, coverage thresholds, dead code, security issues, or any pre-merge checklist. Also use when the user asks "is this ready?", wants a pre-PR review, or needs to confirm nothing is broken after a refactor.

2026-04-105

swift-patterns

Rixmerz/agentcockpit

Swift architecture reference — SwiftUI, UIKit, Combine, async/await, actors, and production best practices for Swift 5.9/6.0 (2024-2025). Use when making architectural decisions, reviewing Swift code, or selecting libraries. Also use when the user mentions iOS development, macOS apps, or Apple platform development.

2026-04-035

ui-patterns

Rixmerz/agentcockpit

UI/Frontend architecture reference - React 19, Next.js 15, Vue 3, Svelte 5, Angular 19, CSS modern features, component libraries, state management, and production best practices for 2024-2025. Use when building frontend UIs, selecting frameworks, reviewing component code, or making frontend architecture decisions.

2026-04-035

ux-patterns

Rixmerz/agentcockpit

UX design reference - research methods, design systems, accessibility (WCAG 2.2, EAA), UX laws, AI-driven workflows, tools (Figma, Penpot), and production best practices for 2024-2025. Use when making UX decisions, reviewing designs, implementing accessibility, selecting design tools, or applying UX principles.

2026-04-035

csharp-patterns

Rixmerz/agentcockpit

C# architecture reference - frameworks, design patterns, ASP.NET Core, Entity Framework, Blazor, Unity, and production best practices for C# 12/13 and .NET 8/9 (2024-2025). Use when making architectural decisions, reviewing C# code, or selecting libraries.

2026-03-235

name	xterm-pty
description	xterm.js 6.0 + portable-pty terminal patterns for agentcockpit

xterm.js + PTY

Overview

agentcockpit uses xterm.js 6.0 for terminal rendering and portable-pty (Rust) for cross-platform PTY management. The PTY runs user's shell, and AI agents are launched as commands within it.

Configuration

xterm.js 6.0 with addons: fit, clipboard, web-links, canvas/WebGL renderers
portable-pty 0.8 (Rust crate)
Terminal: TERM=xterm-256color, 10000 line scrollback
Font: JetBrainsMono Nerd Font, 14px

Data Flow

User types → xterm.onData → usePty.write → ptyWrite IPC → Rust PtyManager.write → PTY master
PTY output → Rust reader thread (4096 byte chunks) → pty-output-{id} event → usePty.onData → xterm.write

Common Patterns

Spawning PTY (Rust)

// PtyManager::spawn creates PTY pair, spawns $SHELL
let pair = pty_system.openpty(PtySize { rows, cols, .. })?;
let mut cmd = CommandBuilder::new(shell);
cmd.cwd(cwd);
cmd.env("TERM", "xterm-256color");
// Clear nested detection vars
cmd.env_remove("CLAUDECODE");
cmd.env_remove("CLAUDE_CODE_ENTRYPOINT");
let child = pair.slave.spawn_command(cmd)?;

Writing to PTY (TypeScript)

import { ptyWrite } from '../services/tauriService';
await ptyWrite(ptyId, data);

UTF-8 Boundary Handling (Rust)

The reader thread buffers incomplete UTF-8 sequences across reads using find_utf8_boundary() to avoid splitting multi-byte characters.

Activity Detection

const { signalOutput, signalUserInput } = useTerminalActivity({
  terminalId,
  threshold: 3000, // ms of silence before "finished"
  onFinished: handleTerminalFinished,
});

Resume UUID Detection

// In TerminalView onData callback
const stripped = data.replace(/\x1b\[[0-9;]*[a-zA-Z]/g, ''); // Strip ANSI
resumeBufferRef.current += stripped;
const match = resumeBufferRef.current.match(
  /claude\s+--resume\s+([0-9a-f]{8}-[0-9a-f]{4}-...-[0-9a-f]{12})/
);
if (match) sessionEvents.emit('resume-detected', { uuid: match[1], terminalId });

Best Practices

Never block PTY writes — send input immediately, do async work (snapshots) after
Buffer incomplete UTF-8 in reader thread — don't emit partial sequences
SIGTERM then SIGKILL on close — give process group time to clean up
Guard 0x0 resize — happens when xterm container gets display:none
Use refs for listeners — prevent re-renders from killing event subscriptions