chore: add Talocode funding and Cua integration plan

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+# These are supported funding model platforms
+
+github: [Abdulmuiz44]

README.md

@@ -347,6 +347,12 @@ We welcome contributions that align with Codra's focus on local-first, secure, a
 
 Please read [CONTRIBUTING.md](CONTRIBUTING.md) before submitting pull requests.
 
+## Support Talocode
+
+Talocode builds open-source workflow layers for builders: coding agents, learning tools, trading intelligence, video workflows, and local-first automation.
+
+If Codra helps you, you can support the work through [GitHub Sponsors](https://github.com/sponsors/Abdulmuiz44).
+
 ## License
 
 This project is licensed under the terms specified in the LICENSE file.

docs/integrations/CUA.md

@@ -0,0 +1,85 @@
+# Cua Integration Plan for Codra Code
+
+## What is Cua?
+
+[Cua](https://github.com/trycua/cua) is an open-source computer-use agent infrastructure that provides CLI/MCP for controlling desktop apps in the background. It enables AI agents to interact with desktop applications through screenshots, clicks, typing, and other UI automation.
+
+## Why It Matters for Codra Code
+
+Cua could power **Codra Code** or **Codra Canvas** by enabling:
+
+- Desktop application control from the terminal
+- Visual verification of code changes
+- Automated UI testing
+- Browser interaction beyond web content
+- Cross-platform desktop automation
+
+## How Cua Could Connect Through MCP
+
+Cua exposes computer-use capabilities through MCP (Model Context Protocol). This means Codra Code could connect to Cua as an MCP server to gain desktop control abilities.
+
+### Possible Commands
+
+- `/cua status` — Check if Cua is available and connected
+- `/cua connect` — Connect to a Cua MCP server
+- `/cua screenshot` — Take a screenshot of the current desktop
+- `/cua click` — Click at screen coordinates
+- `/cua type` — Type text into the focused application
+- `/cua run-demo` — Run a demo automation sequence
+
+## Security Requirements
+
+Desktop automation is powerful but requires strict security controls:
+
+1. **Explicit permission** — Never perform desktop actions without user approval
+2. **No silent execution** — Always show what will happen before doing it
+3. **Audit logs** — Log all desktop actions for review
+4. **Workspace isolation** — Cua actions should be scoped to the current workspace
+5. **Credential protection** — Never enter credentials without explicit user approval
+
+## Roadmap
+
+### v0.2 — Optional MCP Integration
+
+- Add Cua as an optional MCP server
+- Users can connect Cua manually via `/mcp connect cua`
+- Desktop actions require explicit approval
+- Basic screenshot and click capabilities
+
+### v0.3 — Codra Canvas Desktop Control
+
+- Integrate Cua into Codra Canvas
+- Enable visual verification of code changes
+- Support automated UI testing workflows
+- Cross-platform desktop automation
+
+## Security Model
+
+```
+User → Codra Code → MCP → Cua → Desktop
+         ↓
+    Permission Check
+         ↓
+    Audit Log
+         ↓
+    User Approval
+```
+
+Every desktop action must:
+1. Be requested by the user
+2. Show what will happen
+3. Get explicit approval
+4. Be logged for audit
+5. Stay within workspace boundaries
+
+## Status
+
+- **v0.1.x**: Not implemented (planning only)
+- **v0.2**: Optional MCP integration (planned)
+- **v0.3**: Codra Canvas desktop control (planned)
+
+## References
+
+- [Cua GitHub](https://github.com/trycua/cua)
+- [MCP Protocol](https://modelcontextprotocol.io/)
+- [Codra Code](https://github.com/talocode/codra)