sapientinc /PRAXIST
Autonomous research system for measurable, computer-executable research.
★ 5,526⑂ 733◈ 3
5,526
stars
+-7+-11+15
733
forks
–
watchers
–
prs
–
issues
–
releases
3
discussions
README
Praxist: meet your personal R&D team Praxist is an autonomous research system for measurable, computer-executable research. It coordinates parallel research peers, task-owned evaluation, durable evidence, and generation-to-generation synthesis. Praxist treats research as a persistent process rather than a sequence of disconnected prompts. Use it when a project already runs and its objective is measurable, but the best path forward is still unknown. Install Praxist Install the complete runtime integrations and finish first-use setup with one command: bash python3 -m pip install --index-url https://pypi.org/simple "praxist[agents,codex]" && praxist setup --interactive --install-skills codex The local wizard covers the Fair Source License, User Agreement, privacy, runtime profile, masked credentials, Codex skills, writable examples, and readiness checks. It does not select a research project or launch a run. For Claude Code, use the host-specific one-line command. For an agent-managed installation, open Codex: bash codex --yolo Then ask it to install and configure Praxist using the packaged OOBE runbook, and to stop after readiness checks. Before starting research, read the Quickstart and Your First Task. They describe the separate takeover step and the project contract it creates. Choose Codex-native mode to use an existing Codex subscription without an API key. For sustained research, Praxist generally favors open-source model APIs with a high observed cache-hit rate. The setup wizard also supports other API-backed profiles. Use Praxist Through Codex We recommend Codex as the interface for operating Praxist. Praxist is not a replacement for Codex: Codex remains the interactive agent that understands your project, communicates with you, and uses development tools. Praxist adds the persistent research loop, parallel peers, evidence protocols, scheduling, and lifecycle control. After installation, open Codex in the root of an already runnable research project and invoke $praxist-takeover. The takeover skill inspects readiness, creates or repairs the task harness, validates its evaluator and evidence contract, and launches the run after the required gates pass. A precise brief produces a better research plan; include the objective, metrics, constraints, resources, exploration choices, and whether launch is authorized. Example takeover brief text $praxist-takeover Treat the current directory as the existing runnable research project. Verify the baseline and its evaluation path before changing anything. Optimize while preserving . Use peers for up to generations within . Use the runtime and model provider selected during setup. literature search, QD, and generation-zero DIG. Do not download new datasets or replace required project assets. Build a separate task harness with explicit metric directions, baseline provenance, protocol-integrity checks, evidence maturity rules, and justified retention
Top issues
#84[Bug]: Peer runtime shell snapshots capture the provider API key into run artifacts1 comments · 2026-09-01#43Complete end-to-end research loop resume support or document remaining unsupported boundaries1 comments · 2026-09-01#8[Bug]: Valid absolute stop_signal_path is rejected when run_dir is relative0 comments · 2026-08-30#208Notice: Third-party AI-assisted report on PRAXIST published0 comments · 2026-10-26#189[Bug]: rocket_booster_recovery PC harness fails canary — stale FROZEN_HASHES pin for src/plant_adapter.py0 comments · 2026-09-03#83[Bug]: GPU-scheduled task harnesses admit zero evaluation jobs on CPU-only hosts, with no fallback and no error0 comments · 2026-09-01