Back to selected work

Keep command history separate from provider sessions

Engagement
Host Orchestrator · independent project
Period
2026
Stack
  • Rust
  • Tokio
  • Axum
  • SQLite
  • React
  • TypeScript
Command historyConcept preview
  1. 01Recorded
  2. 02Recorded
  3. 03UncertainReconcile before another attempt

An uncertain command is not automatically replayed.

In 30 seconds

Problem

A coding-agent tool needs a durable project history even when provider sessions or execution hosts change.

My part

I develop the Rust core, SQLite persistence, HTTP services and CLI, alongside a React/TypeScript interface.

Result

The core records commands and uncertain outcomes separately from provider sessions, so recovery has a record to reconcile. An uncertain command is not automatically replayed.

Technical decisions

  1. Give the logical conversation its own identity.

    Why
    A provider session is an execution detail, not the complete project history.
    Trade-off
    The core must maintain explicit mappings between conversation and runtime sessions.
  2. Record an uncertain outcome instead of automatically repeating the command.

    Why
    A disconnected host may still be executing it.
    Trade-off
    Recovery may require reconciliation before another attempt.

Operation

The implemented core includes local command and artifact persistence, HTTP/CLI access and execution-admission contracts. I am extending runtime coordination and the shared interface.

Authorship

Independent software integrating official provider runtimes. My contribution covers the local core, execution-admission contracts and the shared interface.

Discuss an engineering role

Open to on-site and hybrid opportunities throughout Spain, and remote opportunities in Europe.

contato@guilhermejansen.com

Guilherme Jansen · Senior Software Engineer · AI Engineer

Back to top