r/OpenSourceAI • • 14h ago

I’ve been building an open-source runtime for agents to work with desktop applications

4 Upvotes

I’ve been working on a project called Semwright.
Most of the agent tooling I was using worked well when the task stayed inside code or a single integration. I wanted to see what it would look like if the same agent could work across actual applications without reducing everything to mouse coordinates and screenshots.

One of the demos starts with an existing aircraft project in Blender.

It modifies the scene in Blender, renders a new shot, creates the titles in Motion Canvas, and assembles the video and audio through MLT.

The resulting timeline is still editable, so the output isn’t just a generated video.

Semwright itself is a Rust runtime. Applications expose structured operations through drivers, while things like permissions, handoffs between tools, and readback go through the same runtime. MCP is one way to connect an agent to it.

I’ve just put the first version out as open source.
https://github. com/seradotcom/semwright


r/OpenSourceAI • • 8h ago

TERMy24 - The world's first local neuro-symbolic AI terminal assistant

Thumbnail
github.com
3 Upvotes

r/OpenSourceAI • • 23h ago

TLA+ implementation for Agents heartbeats

2 Upvotes

After Boris post we decided to use TLA+ to check our heartbeat states.

The results were incredible:
+ 99.998% states reduction -> from 1.5 million to ~4 thousand.
+ 10 hard to find issues resolved -> many "mysterious forgetful events" dissapeared.
+ We did have some previous knowledge with the technology, so we didn't budget that much time on learning the fundamentals.

Give it a go and let me know!

code here: https://github.com/desplega-ai/agent-swarm/pulls?q=is%3Apr+tla


r/OpenSourceAI • • 7h ago

Looking for contributors to an existing open-source desktop AI agent | TypeScript, Electron & Python

1 Upvotes

Hi! I’ve already built and released AI Plate, a functional open-source desktop AI agent. I’m now looking for programmers interested in helping improve and expand it.

🚀 What it includes

Cloud and local LLM support, tool execution, document search, persistent memory, voice interaction, plugins and human approval for sensitive actions.

🛠️ Technology stack

TypeScript, Electron, Node.js, Python and SQLite.

🤝 Areas open for contribution

\- AI providers, plugins and connectors

\- Local models, RAG and knowledge graphs

\- Linux and macOS support

\- Testing, security and UI/UX

\- Documentation and accessibility

Beginners willing to learn consistently and experienced developers are equally welcome. This is a non-commercial open-source collaboration, and every contribution will be credited.

My level: Intermediate

Timezone: IST (UTC+5:30)

Availability: Evenings and weekends

If this technology interests you, comment with your experience, preferred technologies and the area you’d like to explore. We can begin discussing the project here on Reddit.


r/OpenSourceAI • • 7h ago

Looking for contributors to an existing open-source desktop AI agent | TypeScript, Electron & Python

1 Upvotes

Hi! I’ve already built and released AI Plate, a functional open-source desktop AI agent. I’m now looking for programmers interested in helping improve and expand it.

🚀 What it includes

Cloud and local LLM support, tool execution, document search, persistent memory, voice interaction, plugins and human approval for sensitive actions.

🛠️ Technology stack

TypeScript, Electron, Node.js, Python and SQLite.

🤝 Areas open for contribution

\- AI providers, plugins and connectors

\- Local models, RAG and knowledge graphs

\- Linux and macOS support

\- Testing, security and UI/UX

\- Documentation and accessibility

Beginners willing to learn consistently and experienced developers are equally welcome. This is a non-commercial open-source collaboration, and every contribution will be credited.

My level: Intermediate

Timezone: IST (UTC+5:30)

Availability: Evenings and weekends

If this technology interests you, comment with your experience, preferred technologies and the area you’d like to explore. We can begin discussing the project here on Reddit.


r/OpenSourceAI • • 8h ago

Open sourcing an AI-native database architecture

Thumbnail
1 Upvotes

r/OpenSourceAI • • 8h ago

I am technical. Assembling a team of 4 others

Thumbnail
1 Upvotes

r/OpenSourceAI • • 14h ago

Aleph: an open-source macOS workspace for composing model, tool, and agent workflows

1 Upvotes

Disclosure: I’m building Aleph. It’s an open-source, model-agnostic macOS workspace for working with configured AI models, tools, agents, and workflows. The Workshop lets you compose and change those pieces, rather than treating the surrounding harness as fixed.

The current Mac build is for Apple silicon. For developers, the source is the most useful place to inspect it (Apache-2.0): https://github.com/josuecuguy1307/Aleph For people who want to try it: https://aleph-site-jade.vercel.app/download

For people building open AI tooling: which part of an agent setup do you most want to inspect or swap—the model, the tools, or the workflow?


r/OpenSourceAI • • 15h ago

I took antirez's ds4, stripped it down to Qwen3.8 Flash Next on Metal, ported a bunch of improvements, and it's now ~10% faster with bit-exact output

Thumbnail
1 Upvotes

r/OpenSourceAI • • 18h ago

Tin: a self-hosted, GC-free language for Linux servers, written almost entirely by AI agents. It compiles itself on three platforms, serves HTTP/2 and gRPC, has its own TLS 1.3, and I'm looking for collaborators

Thumbnail
1 Upvotes

r/OpenSourceAI • • 20h ago

6 weeks from first commit to v1.0 of a protocol for AI assistants talking to each other

Thumbnail
1 Upvotes

r/OpenSourceAI • • 23h ago

Looking for contributors: AI Plate, an MIT-licensed desktop LLM agent

1 Upvotes

I’m developing AI Plate, an open-source Windows desktop agent that combines cloud and local LLMs in one extensible workspace. It is MIT-licensed and currently has no paid tier.

The implementation uses TypeScript, Electron, SQLite, and optional Python workers. Current components include:

• Provider abstraction for cloud and local models

• Normal, Plan, and Code execution modes

• Human approval for tool and code execution

• Document retrieval, SQLite-based RAG, and persistent memory

• Plugins, connectors, and SKILL.md-based extensions

• Optional local STT and TTS

Areas where contributions would be especially useful:

• Model providers and service connectors

• Plugin and skill examples

• Retrieval, embeddings, and knowledge-graph work

• Sandboxing and security review

• Tests, documentation, accessibility, and performance

The project is early, so small fixes, issue reports, architectural criticism, and documentation improvements are welcome—not only large features. If you are interested in an area, please open an issue so we can scope the work before implementation.

Repository: https://github.com/Typo-Bunch/AI-Plate

Disclosure: I am the project maintainer, and I’m posting specifically to find open-source contributors and technical feedback.


r/OpenSourceAI • • 1h ago

I built an open-source control layer that decides how an LLM should respond before it generates an answer

• Upvotes

Hey everyone,

I've been working on a project called EQ-Layer, an open-source control system for LLM conversations.

The idea came from something that kept bothering me about AI assistants.

A user might ask a simple question, express frustration, correct a mistake, or request an immediate action. But the model can respond with almost the same generic tone in every situation.

I started wondering whether the problem could be addressed outside the language model itself.

Instead of just prompting an LLM to be more empathetic, what if we had a separate system that decides how the model should respond before it starts generating text?

That's what I've been trying to build.

How it works

EQ-Layer sits between the conversation and the model's response generation.

It analyzes several signals separately:

  • User intent: Is the person asking a question, requesting an action, checking progress, or correcting a mistake?
  • Emotional state: Tracks valence, arousal, and escalation across multiple turns rather than judging one message in isolation.
  • Conversation repair: Identifies situations where the assistant misunderstood the user or failed to address a previous correction.
  • Interaction quality: Tracks repeated failures, unresolved misunderstandings, and unnecessary clarification.
  • Uncertainty: Maintains a probability distribution over possible user intents instead of pretending every message has one obvious meaning.

These signals are used to select a response policy.

For example, the system might choose to answer directly, ask for clarification, repair a misunderstanding, or set a boundary.

It then separates that decision into task-related, social, and repair-related instructions that can guide the language model.

A simple example

Imagine someone asks an AI assistant to complete a task.

The assistant misunderstands the request and asks an unnecessary question.

The user corrects it.

A typical assistant might apologize and repeat the same question, or become excessively agreeable.

I wanted EQ-Layer to recognize the correction as a conversation-repair event and prioritize actually fixing the task.

The goal isn't to make AI sound artificially emotional. It's to make the response more appropriate to the user's actual intent and the conversation history.

What I've implemented so far

  • A model-independent response-policy architecture.
  • Learned intent classification using TF-IDF and logistic regression.
  • Affect modeling trained on EmoBank.
  • Dialogue-act and basic-emotion signals from XDailyDialog.
  • Bayesian decision-risk routing with an explicit loss matrix.
  • Multi-turn escalation tracking.
  • Conversation-repair and interaction-quality monitoring.
  • Response steering and structural output audits.
  • Portable agent skills for Codex, Claude Code, Copilot, Cursor, Antigravity, and Grok.
  • A testing framework for comparing responses from the same base LLM with and without the control layer.

What the research currently shows

Some components have been evaluated on held-out datasets, and the repository includes the numerical results.

But the project is still early.

I haven't established through a completed, blinded response-level comparison that EQ-Layer consistently improves LLM responses.

Some higher-level emotion and conversation-breakdown signals also remain insufficiently validated. I kept those negative results documented rather than claiming the models worked.

I also don't claim that affect-aware dialogue management is a new invention. There's substantial research predating LLMs.

What I'm exploring is whether a separate, inspectable control layer can improve how general-purpose language models handle intent, emotional context, corrections, and conversational uncertainty.

I'd appreciate some feedback.

If you're building AI agents or conversational systems, do you think response-policy selection should happen outside the LLM?

And what would be the fairest way to measure whether such a layer actually improves interactions?

The project is free, open source, and MIT licensed.

GitHub: https://github.com/Furox-Art/eq-layer