wip: snapshot das alterações não commitadas (2026-10-20)
Origem: D:/Documents/Github/PiAgentUI/PiAgentUi Arquivos omitidos (segredos, bancos de dados, logs, >50 MB): 4
This commit is contained in:
1 parent
b3489e1ede
commit
98b5db029f
70 files changed
+9466
-9191
No files matched your search
@@ -135,6 +135,16 @@ PiAgentUI
|
||||
|
||||
The UI should not invent runtime state when Pi already knows the answer. PiAgentUI can cache and enrich data for UX, but Pi remains authoritative for agent behavior.
|
||||
|
||||
### Fast session creation
|
||||
|
||||
New-session entrypoints render an optimistic local session immediately, then reconcile that temporary `optimistic-session:*` ID with the real Pi runtime session when the backend responds. This separates time-to-visible-session from backend latency: the user sees a usable chat surface synchronously, while message sending waits for the authoritative Pi session ID.
|
||||
|
||||
If runtime creation fails, PiAgentUI rolls back the optimistic session and returns control to the composer so the draft can be retried instead of disappearing into a failed route.
|
||||
|
||||
### Extension compatibility
|
||||
|
||||
Pi packages that declare `pi.extensions` remain the supported extension path. OpenCode-style manifests are detected and labelled as partial compatibility, but PiAgentUI does not execute those entrypoints yet. Execution requires a future sandbox and permission model so untrusted extension code cannot access local files, credentials, or agent state without explicit policy.
|
||||
|
||||
## Tech stack
|
||||
|
||||
| Area | Stack |
|
||||
|
||||
Reference in new issue
Block a user