praxis
Your workspace for AIBeta coming soon

Your goal.A whole team.

Bring your ideas to life. Connect agents, models and tools for code, automation and creative work.

  • Planner
  • Builder
  • Reviewer
  • Tester

One goal.
Connected capabilities.

Praxis / Code / Workflow editorConfigured example ↗
Praxis visual workflow editor — a configured graph with planning, a human decision, execution and conditional connections.
01 Code02 Wingman03 Automations04 Bots05 Studio06 Your Space

A good answer is a start.
What you do with it matters.

  1. 01 / GOAL

    Set your direction.

    Add project context and define what a finished result should do.

  2. 02 / TEAM

    Choose how to work.

    One agent, a pair or a team. The right models for the right roles.

  3. 03 / ACTION

    Move into execution.

    Files, tools and connected stages in one workspace.

  4. 04 / RESULT

    See what was delivered.

    Review changes, tests and evidence before accepting the result.

Power where it matters

Think with the best.
Build for less.

Not every step needs your most expensive model. Build a cascade: a strong model for analysis, a cheaper one for execution. Save expensive-model tokens for the decisions that need them.

01 / Analysis and planning

Understand the problem first.

Use Claude Code, for example, to analyse and plan in a custom workflow. Define what to build and what a finished result should do.

02 / Execution

Match the cost to the task.

Hand clearly defined steps to a cheaper API, a model with a free allowance or a compatible local model.

03 / Verification

Let the result prove the quality.

Review the work and fix what needs attention. Bring a stronger model back for harder decisions when needed.

This example uses a custom workflow. Available connections, free allowances and limits depend on the mode and provider. Local models require your own hardware. Savings depend on the task, context and number of revisions.

Praxis Studio

Your next story.
From script to screen.

From script and storyboard to images, clips and sound. Develop each shot and keep a history of your creative decisions.

Praxis Studio — the real Vera project storyboard, showing frames from the Preparation scene.
Vera / a real project by the creator · storyboard and materials in progress
Explore Studio
Work takes many forms

Less switching.
More creating.

Code, everyday tasks, processes and creative projects. Six modules, shared context and the freedom to choose your tools.

Explore the details

Capabilities that
make a difference.

Move from a broad idea to a specific capability. Open the catalogue, search for a topic and see how Praxis fits your way of working.

Explore every capabilityCode, Studio, automations and shared tools

Code — work and collaboration

01 /
  • Conversations, attachments and Steer

    Streaming responses, task cancellation and additional instructions during execution. Other chats can work in the background; notifications report a finished result or a decision that needs your attention.

  • Context from the actual project

    Technologies, manifests, scripts, Git and facts with sources. For Unity, this also includes the editor version, packages and build scenes.

  • Modes that fit the task

    Standard, Direct, Analysis, Expert Panel, Autopilot and Syzyf. You can require plan approval before execution.

  • A single agent, Pair, Team or Auto

    Pair adds an independent reviewer and revision rounds. Team divides the work and integrates the results.

  • Implementation alternatives

    Compare solutions prepared in isolated copies. You choose an alternative before it is applied; a supported Git project is required.

  • Expert Panel

    Independent specialist opinions, evaluation of arguments and a synthesis. Explore a solution or assess an idea in read-only mode.

  • Live progress and dependencies

    The task list shows agents, statuses, dependencies and reasons for blockers. It reports progress; it is not proof that the result is ready.

  • Diffs and Change Vault

    Compare changes from the last prompt or across the project. Checkpoints, restoration and protection for later edits without resetting Git history; also available outside a repository.

  • Result acceptance

    The goal, criteria, verification commands, evidence from the current task and limitations. Later changes invalidate earlier verification results.

  • Visual before and after

    Point out an issue on a page and compare views side by side or with a slider.

  • Conversation context

    Context usage, bookmarked responses and continuation in a new chat with transferred context and a transcript.

Autopilot and Syzyf

02 /
  • Autopilot: from a goal to a plan

    The Deep Agents coordinator assesses the task, selects models and assigns work, builds a plan with criteria and dependencies, and submits it for independent review.

  • Autopilot: execution and acceptance

    Agents can use different connections. Stage checks and final acceptance address the original goal. Stages in the isolated copy run sequentially.

  • Requested version control operations

    Simple version control operations can be delegated to one agent in the current project, with independent verification. Publishing changes requires an appropriate instruction.

  • Syzyf: a queue of improvements

    Project mapping, a queue of small tasks, dependencies, separate implementation and testing agents, revisions and a final assessment of the whole result.

  • A defined scope for autonomy

    Limits on time, tasks and rounds. Perks set the direction: stability, appearance, performance or new mechanics. Syzyf saves the queue and supports explicit resumption.

Wingman — context and everyday work

03 /
  • Start a conversation without a project

    History, search and saved drafts. Start with one task or add context from a larger project.

  • Project context and previous decisions

    Files, facts, saved knowledge and conversation history from the relevant Code project. The history tool retrieves earlier decisions.

  • An assistant beside a page or window

    Use the built-in browser, a selected Chrome tab or a shared app window. Switching the preview preserves the task description.

  • Documents and PDF export

    Create and edit text and Markdown documents, save with version checks and export to PDF.

  • Explicit preference memory

    Read preferences, propose saving them or forget them. You approve changes, and the local memory store is encrypted.

  • Praxis Assistant across modules

    A floating conversation controls available app operations: settings, projects, queues, boards, perks, Studio and Creator.

Automations — processes and schedules

04 /
  • Boards, task backlog and files

    A separate workspace for recurring work. Each card holds a goal and context; its column defines the instructions for the current stage.

  • Custom stages and transition rules

    Editable columns, drag-and-drop cards, conditions and templates. A stage can run a prompt, wait for manual execution or complete the process.

  • One-time and recurring schedules

    Times, days, intervals and time zones. Delays do not trigger a burst of missed runs.

  • Pause, resume and history

    Pause a card, a board or future starts. History preserves instructions, results and statuses; a resumed stage starts again with its history.

  • Tasks from every project

    A shared queue handles tasks from different projects regardless of the view you are using. Praxis must be running and the required tools must be available.

  • Processes managed through conversation

    Manage processes through the assistant, CLI and MCP. Deduplication and a separate review session help build workflows such as reproduce → fix → validate.

Bots — work in the browser

05 /
  • Role, goal, model and account

    Custom instructions, materials, a start URL and an account label for each bot.

  • Separate, persistent profiles

    Browser sessions and cookies are separate for each bot. You handle sign-in and passwords.

  • Approvals and automatic execution

    Clicks, typing and image uploads require approval by default. Optional automatic execution stays within the saved goal.

  • A log of actual operations

    Arguments, results and execution statuses. An uncertain outcome requires checking rather than blindly repeating the action.

  • Worker pool and queue

    Tasks for the same account run sequentially; different accounts can work in parallel. Subsequent runs require the app to remain open.

  • Materials and a proxy for each bot

    You select the images, and upload checks the file. An HTTP, HTTPS or SOCKS5 proxy configures browser traffic for the selected bot.

Studio — from a brief to a moving shot

06 /
  • Storyboard, script and animatic

    A brief, style, scenes and shots. Views for the storyboard, shot list, script, animatic, materials, characters and editing.

  • Characters and reference library

    Appearance, personality, speaking style, reference materials and voice. Characters can be copied between projects.

  • Details and control for every shot

    Action, camera, movement, cast, location, prompt, dialogue and duration. Locks, ratings, filters and statuses for materials that need review.

  • Image generation and editing

    New images, edits to a specific image, more similar images and multiple variations. Use references and a base image.

  • Version history and result selection

    Saved prompts, the source image for an edit and before/after comparison. Explicitly assigning a result to a shot protects approved materials from replacement.

  • Image → clip

    “Animate shot” creates video from an image. The clip and source image remain separate assets; the animatic combines clips with still frames.

  • An assistant with project context

    Feedback on prompts, prompt refinement, project editing and generation requests through controlled operations.

  • Import and transfer materials

    Images, video, audio, storyboards and references. Copy or move storyboards between projects.

Studio — audio, export and providers

07 /
  • Voices, effects and music

    Generate character lines, sound effects and instrumental music.

  • Narration for a shot or the whole film

    Separate narration tracks. Export can combine clip audio, dialogue, narration, music and effects.

  • MP4, subtitles and a game asset package

    Local rendering with FFmpeg/FFprobe, an SRT file, a manifest and a media package. Handoff to Code prepares instructions with the local export path.

  • ChatGPT and Gemini

    Generate and edit images using text and references. ChatGPT uses Codex sign-in and the account quota; Gemini requires an API key.

  • Local or remote ComfyUI

    Separate image and video workflows, base images, references and saved remote task IDs.

  • Runway and ElevenLabs

    An image-to-video adapter plus voice, sound effect and instrumental music generation.

  • Your own HTTP/JSON API

    Profiles for images, video and speech: authentication, status polling and result mapping. Templates include Seedance/BytePlus and MiniMax.

  • Service and tool setup

    Providers require your own account or configuration. Paid adapters depend on service permissions; FFmpeg/FFprobe must be available locally.

Your Space — tools from a conversation

08 /
  • Creator: from a need to a proposal

    An interview, attachments, context and idea refinement. Mini-app building, a real preview and explicit activation of a saved version.

  • Custom HTML/CSS/JS tabs

    Navigation, forms, local collections and files. Declared AI actions show progress and support cancellation.

  • Conversation beside the app being built

    Add instructions during generation, get suggestions for further development and undo suggestions.

  • Versions and data preservation

    Interface history, compatible rollback, separate test and active data, archiving, restoration and full-screen mode.

  • Validation in a real Electron runtime

    Schema and JavaScript checks plus a hidden test that clicks, types and creates a record. Detected errors are passed to the next revision attempt.

  • An isolated view and controlled SDK

    A separate WebContentsView and session with limited data and AI access. A completed local view works without a model running continuously.

  • Multiple generation engines

    Supported ChatGPT/Codex, Google and Claude Code accounts, or local models. Available actions and tools depend on the selected engine.

Models and execution engines

09 /
  • Accounts, APIs and local models

    Codex/ChatGPT, Claude Code, Google, OpenCode, compatible API gateways and local servers. You choose the providers.

  • An open catalog of connections

    Includes Ollama, LM Studio, LocalAI, vLLM, LiteLLM, OpenRouter, Groq, Gemini API, OpenAI API, DeepSeek, xAI, Vercel AI Gateway, Azure and a custom Responses endpoint.

  • Manual or automatic selection

    Model-dependent reasoning settings and profiles for quality, savings and oversight. Separate models for analysis/planning, execution and verification.

  • Routing with an explanation

    Selection considers the current catalog, availability, account quotas, benchmarks, short tests and the needs of the task.

  • Budgets and quota renewals

    “Free only” or “Within my accounts.” If no permitted model is available, the payment scope is not expanded automatically. “Use available limits” favors permitted models with quotas approaching renewal.

  • Fallback without blind retries

    Switch an unavailable model before substantive work begins, preserving permissions and budget. A tool action with an uncertain outcome is not automatically repeated.

  • Praxis Native: a custom runtime

    A local model loop, files, a macOS terminal, background processes, helpers, skills, long-context handling and sessions on disk. Requires a compatible local model.

  • Visual workflow editor

    Connect Start, Model, Your decision, Condition and End blocks. Set roles, instructions, models and project access; add branches and bounded revision loops. Save templates and reuse them for later tasks. Custom graphs run on LangGraph, with SQLite checkpoints and controlled resumption.

  • Usage and execution visibility

    Tokens, costs and explicitly labeled estimates or unavailable data. Optional Langfuse; including prompt content requires a separate setting.

Tools, integrations and control

10 /
  • Built-in browser

    Navigation, page inspection, clicks, typing, keys and screenshots. Separate or shared profile groups and data clearing.

  • A selected Chrome tab

    Explicit MCP connection and tab selection. Closing that tab does not automatically move the agent to another page.

  • Share an app window

    App Share on macOS and Windows: you choose one window; the agent reads controls and screenshots and uses controlled actions. System permissions are required.

  • Approvals, Stop and sensitive actions

    Approval policies, password/PIN protection and explicit decisions for sensitive effects. Stop execution and review uncertain outcomes.

  • MCP and external tools

    stdio and Streamable HTTP transports, resources and prompts. Native supports OAuth for compatible connections.

  • Control Praxis through CLI and MCP

    The local control API provides access to projects, chats, queues, perks, boards, Studio and Creator. The in-app assistant uses it too.

Projects, knowledge and organization

11 /
  • Project environment preparation

    Technology detection and recommendations for bundled skills. You choose what to install, and existing skills are preserved.

  • Learn from your own work

    Project and history analysis suggests skills, perks and reusable actions, with reasons and sources. You can accept or reject each suggestion.

  • Your own working rules

    Perks, skills and an overarching doctrine. Settings and instructions can apply to one project or the whole app.

  • Local project knowledge

    An optional LanceDB index and embeddings from a local server. References to sources and lines, with ignored files respected.

  • Code prompt queue

    Start now, after the current task, after the project queue or at a set time. Prompts retain attachments and settings; project tasks can run sequentially or in parallel.

History, data and personalization

12 /
  • Import conversations

    Selected Claude Code and Codex conversations, or a ChatGPT export, copied as text to local history. Import does not resume the original tool session.

  • Transfer selected data

    Export and import selected history, settings, Wingman and Your Space data. The package excludes accounts, keys, external repositories, Studio and bots.

  • Local storage and keys

    History and projects are stored locally, and keys are handled by an encrypted store. Cloud models receive the context needed for the task.

  • Appearance, language and notifications

    Light, dark or system theme, visual styles, reduced motion and a completion sound. The interface is available in Polish, English and German.

  • Limits and organized history

    Settings for execution limits, archiving and app behavior. You remain in control through the app settings.

Generation and model availability depend on configured providers, accounts and local tools. Automations run locally while Praxis is open. Project data is stored locally; using an external model may require sending it the task context.

Designed for real work

Freedom to act.
Control over the process.

Local storage, lasting history and visible stages of work. Under the interface: an architecture that connects models, tools and control over the result.

ElectronReactTypeScriptLangGraphSQLite
  • The app and your data

    A React interface in Electron. Projects, conversations and settings stored locally.

  • Models in one process

    Agent roles, provider connections and a custom execution environment for local models.

  • Keep work moving

    Saved stages, task history and resumption. Separate queues for scheduled work and work in progress.

  • Permissions and control

    Mini-apps in separate views. Controlled data access, operation checks and action approvals.

  • Validation

    Unit tests, integration tests and scenarios in the real Electron app. Check results tied to the task.

From a goal to a checked result

01

Plan.

The goal, project context and completion criteria.

02

Execute.

The right model, tools and agent roles.

03

Verify.

Review the result, run tests and iterate on fixes.

04

Deliver.

Changes, artifacts and evidence against the criteria.

Execution depends on the selected mode. You retain access to the plan, history and control over the work.

The waitlist

Be among the first.
Discover Praxis in beta.

Leave your email. I’ll let you know when the beta is available. No newsletter, just the beta notification.

Your data is managed by Filip Rudziński. Your address will only be used for the beta notification and kept until it is sent or you withdraw your consent. To withdraw consent and delete your address, email kontakt@praxisagent.app.

Contact / the creator of Praxis

Good products
start with a conversation.

I’m Filip Rudziński. I’m building Praxis. I design and develop tools that bring AI agents, automation and desktop applications together.

I’m open to project collaborations and employment opportunities building AI products. I’d be happy to talk about the problem you want to solve.

Collaboration and opportunities

Your next idea needs a builder.

Developing a product, growing a team or interested in collaborating on Praxis? Send a few words about what you’re working on.

kontakt@praxisagent.app

Create with AI.
On your terms.

Beta coming soon. Get notified when it’s ready ↗

Back to top

Privacy and cookie policy

Updated: 27 October 2026. The data controller for this Praxis website is Filip Rudziński. Contact: kontakt@praxisagent.app.

Site operation and security

The site is hosted through Sites (OpenAI) and Cloudflare. Infrastructure providers process technical connection data, including IP addresses, to deliver the site and prevent abuse. The basis for processing necessary security data is the controller’s legitimate interest (GDPR Article 6(1)(f)). We do not store IP addresses in the analytics database.

Browser technologies

Optional analytics

With consent, we count the UTC day, language, approximate country supplied by the host when available, traffic source category, device type and a category for the recognised client. Events are pageviews, engagement after at least 20 seconds of visible time and interaction, and clicks leading to the waitlist. These are aggregate counters, not a person’s history. Bot detection is approximate; a regular browser does not prove that a visitor is human.

We do not store full page or referrer URLs, raw user-agent strings, user identifiers, form contents in analytics, session recordings or device fingerprints. We do not link analytics to waitlist email addresses. Optional analytics relies on consent (GDPR Article 6(1)(a)). Detailed aggregates are removed after 365 days on the next write; historical daily totals without these categories may remain. DNT/GPC signals are respected.

Waitlist and contact

With separate consent, we store your email address, language, signup date and consent version to notify you when the beta is available. Your address is kept until that notification is sent or you withdraw consent. Signing up is voluntary and does not require analytics consent. There is no newsletter. Contact the controller to withdraw consent and delete your address. Correspondence is handled to answer your enquiry and carry out any agreed collaboration.

Providers and your rights

OpenAI/Sites and Cloudflare provide the infrastructure; contact email is handled through OVH and Gmail/Google. Providers may process data in different countries, including outside the EEA. Their policies describe processing and safeguards: OpenAI, Cloudflare, OVHcloud, Google.

You can change your choice at any time using “Cookie settings” in the footer. Withdrawal stops future analytics without affecting the lawfulness of earlier processing. Aggregate counters cannot be attributed back to a person. Where applicable, you have rights of access, rectification, erasure, restriction, portability and objection, and may complain to the Polish data protection authority (UODO). Send requests to the controller’s contact address.

Praxis application screenshot

Open original

Your privacy

Privacy and cookie policy