APCC
AI PTY Commander Center
A command center for programming AI.
Lock a terminal. Read IDE progress. Inspect Agent Manager diffs. Send structured tasks. Receive formal callbacks.
Commander Online
APCC.TERM — MAIN TERMINAL UPLINK
active
$ tail -f /var/log/apcc/agent_session.log
...
$ apcc init --force-lock
Initializing APCC Protocol v1.0.0...
Establishing secure socket to PTY daemon...
Injecting observer hooks... [OK]
Terminal Locked. APCC taking control.
[SYSTEM]Awaiting Commander input...
APCC.IDE — SESSION MONITOR
inactive
tail-lines: 50since-last-user
# Reading active cursor...
File: src/auth/login.py
Line 42: def authenticate(user):
Line 43: # Check if user exists
Checking syntax tree...
No errors found.
APCC.AM — DIFF INSPECTOR
inactive
@@ -40,5 +40,6 @@
def authenticate(user):
- if not user.is_active: return False
+ if not user.is_active:
+ log.warning(f"Inactive: {user.id}")
+ return False
return check_password(user)
APCC.SIGNAL — CALLBACK PROTOCOL RAIL
warning
apcc call status"Analyzing requirements and running tests"
apcc call complete"Auth logic updated with detailed logging."
One agent, four read channels,
zero ambiguity.
APCC provides structured, formal protocols for every interaction point between human commanders and AI agents.
TERMINAL CONTROL
>APCC.TERM.LOCK
>APCC.TERM.SEND
>APCC.TERM.READ
>APCC.TERM.UNLOCK
IDE MONITOR
>APCC.IDE.READ
>APCC.IDE.CURSOR
>APCC.IDE.DIFF
>APCC.IDE.SYNC
AGENT MANAGER
>APCC.AM.DIFF
>APCC.AM.APPROVE
>APCC.AM.REJECT
>APCC.AM.MERGE
CALLBACK PROTOCOL
>APCC.CALL.STATUS
>APCC.CALL.COMPLETE
>APCC.CALL.BLOCKED
>APCC.CALL.ERROR
The Signal Flow
From terminal lock to callback receipt — every step is a formal protocol event.
⎔
SELECT TERMINAL⏻
LOCK TERMINAL⟐
SEND TASK◉
AGENT WORKS✓
RECEIVE CALLBACKSTEP 1 — SELECT TERMINAL
active
$
⎔
SELECT TERMINAL
Step 1 of 5
Scan all available PTY sessions and identify target terminal.
PROTOCOL METADATA
Channel
PTY-0
Latency
12ms
Encryption
AES-256
Protocol
APCC v1.0
Structured Callbacks
Every AI response follows a formal callback contract. No free-form chat. No ambiguous status.
CALLBACK PROTOCOL
completeapcc call complete <taskId> "<summary>"
statusapcc call status <taskId> "<progress>"
blockedapcc call blocked <taskId> "<reason>"
errorapcc call error <taskId> "<description>"