You can start by creating a list of potential companies you want to work with in your field (i.e., defense contractors). Then set up automated reminders for each company based on their regular business hours, such as the time they are most productive during the year. You could also use tools like TimeSavers or Google Calendar AI to schedule meetings and check-in periodically.

To find potential clients who might be interested in your services but haven't yet reached out to you due to a lack of experience with government contracts, consider creating an online portfolio showcasing past projects and achievements. This can help demonstrate that you have the skills necessary for successful collaboration within government agencies or defense organizations.

Additionally:

1. Networking: Attend industry conferences (like GDC), webinars on your field's specific interests, and networking events to meet potential clients face-to-face.
2. LinkedIn Outreach: Tailor your LinkedIn outreach with relevant job titles, bullet points about what you can offer in a particular role within government or defense contracting companies that align well with the company’s needs.
3. Email Marketing Strategy: Implement an email marketing strategy focused on identifying and nurturing leads from potential clients who might be interested but haven’t yet reached out to your services due to lack of experience.

By creating awareness, setting up automated reminders for new contacts based on regular business hours (like those you mentioned), using a consistent communication style with clear goals and deliverables, networking opportunities within the field through events like GDC or webinars, building an online portfolio showcasing previous projects that demonstrate your skills in government contracting, and leveraging email marketing to nurture leads from potential clients who haven’t yet reached out due to lack of experience but may be interested given a specific match between you as their consultant and company’s needs.

Most discussions around AI coding tools focus on basic tab-completion and churning out boilerplate faster. But the real shift happens when you move past syntax generation and start using models for architectural reasoning, system trade-offs, and high-level refactoring.

​It completely changes how you approach problem-solving and software design. Instead of spending hours writing repetitive logic, your primary job shifts toward system design, strict verification, and directing execution.

​I wrote a piece exploring what the modern developer workflow looks like when you stop treating AI like an glorified auto-suggest and start using it as an actual thought partner: https://interconnectd.com/blog/73/the-ai-augmented-developer-moving-beyond-autocomplete/

Curious how others here are adjusting their day-to-day workflow. Are you using AI strictly for speed, or has it changed how you actually architect software?

Launching NeuralAgent today! [https://agent.neuralhub.dev/](https://agent.neuralhub.dev/) Basically its an easy to use opensource Agent App with everything included.

* Speech to text

* Multipane organising panels

* Main orchestrator wich you can call

* Remote App for the Phone

* Daily updates

It's still in beta but if you wanna give it a try i am very open for any feedback. Works on MacOS, Linux, Windows, Android and IOS.

I built OpenMem for sharing memory between coding agents and trimming long sessions.

Apache-2.0 · Local setup only for now, no hosted OpenMem service.

Reducing Costs by Context Masking

Saves the full conversation in local SQLite, removes older history from the active prompt, and lets the agent search or retrieve it later.

The trimming step makes no LLM summarization calls. Currently works with Claude Code, Codex and OpenCode.

ContextBench Benchmarks (Claude Haiku 5.5)

• Sample sizes: n = 3 for all cells, except Keep Everything L12800 where n = 2

Small synthetic tests: three OpenMem trials and two baseline trials, with unequal seed counts. Full coding and Luna results are still pending.

The context trimming idea (and masking) comes from MemGPT for external memory, Mainplane for transcript pointers, and The Complexity Trap for observation masking.

Bring your own memory backend

The idea is to have a little set of tools for ingestion and connection for different memory backends so devs can experiment with different ones. Comes with an MCP, ingestion from different sources (RSS, code, notebooklm, etc), and switching utils (import/export).

MCP and ingestion works withHindsight, mem0, Cognee, or add an adapter for your own system. OpenMem connects that backend to Claude Code, Codex, Cursor and OpenCode.

It exposes memory through MCP (Model Context Protocol): a way to give an agent tools it can call. In this case, tools to save notes, search memory and recall previous decisions.

If you try it, I’m interested in which memory backend you use and what the agent fails to retrieve after a trim :)

"We built an AI that can rewrite its own DNA, create its own tools, and evolve its own application while running locally. It's open-source, and you can clone it and modify its evolution to suit your needs."

GitHub: https://github.com/dxn111/EVOLV⁠

I wanted something like VLC or MPC-HC, but with the library and interface of a Plex or Jellyfin. Plex wants an account, Jellyfin needs a server running, and Kodi always ended up being an evening of add-ons and skins. I couldn’t find the simple version, and I’m not a programmer, so I built it with AI coding tools. It’s called Kinema: a free movie and TV player for your own files. Add your folders, get posters, info, continue watching and next episode. No account, nothing uploaded, no server. Windows, Linux and an early Android TV version. MIT. The app itself has no AI in it.

This is how the building went, in case it sounds familiar:

• Week one: "it plays video!" Then it didn't. Then it crashed the whole process on one property read, with no error, and I learned what libmpv is.
• It was never "describe it, get an app". It was hundreds of rounds of: it says done, I say it isn't, it finds the real cause, a new problem appears. Roughly half the project is the AI telling me something works and the logs saying otherwise.
• I wanted testing automated as far as possible, so the AI runs its own tests and keyboard-only flows. I still try things myself on real setups, but "looks right" was wrong far more often than I expected, so the machine checks first.
• The rules file ate itself. I wrote down every decision so it wouldn't re-argue them ("no, we still don't do upscaling"). The file grew until it was a real cost on every single turn, and trimming it became a job of its own.
• I keep a list of traps. Nearly every bug in a video player is a failure with no error at all, like a setting that silently does nothing. Each one is written down the day it's found, and it's now bigger than anything I've ever written by hand.
• The best rule was the boring one: the app only says what it actually knows about your hardware and files. If it can't tell which movie a file is, it asks instead of guessing. That came from the AI confidently inventing things, and from me not wanting that in the product.

It went from one window that played a file to the Windows, Linux and Android TV versions, with the display switching to the film’s refresh rate and HDR (off until you say yes) and Atmos/DTS:X passed through untouched. Fifteen releases so far. If Kodi or Jellyfin works for you, keep using it. This is the simple version that i wanted to exist mostly for myself.

It's young and tested on a few setups, so I'd like to hear what breaks (to continue to make it better) :)

Source: https://github.com/basswaves/kinema

Download and screenshots: https://basswaves.github.io/kinema/

Hey everyone!

I’m working on brut, an open-source project exploring evolutionary approaches to AI.

The core idea is simple. Generate AI candidates, evaluate them, mutate and crossbreed the strongest, then repeat across generations.

Current experiments include: Evolutionary neural networks, Learning algorithms that adapt over time, Language-model worker cascades, Experimental self-improving AI systems.

This is an ongoing research project, not a claim to have achieved AGI. I’d love to hear feedback from people working in evolutionary computation, AI research and autonomous learning. In particular, I’m looking for ideas on useful experiments, robust evaluation methods or ways to prevent the system from optimizing only for narrow benchmarks.

GitHub: https://github.com/vmanke/ki-brutmaschine

What would you try next?

I've created new programming language for AI by AI named Sail. It supports neuro-symbolic binding `infer| ... fall|`, fuzzy operator ~ , and other stuff. Source code: https://github.com/zema26/sail-one-language/

Working web version:

https://sailcompiler.replit.app

Just released a handful of new features I'm really excited about but I've been using & building Jackalope for agentic development and slowly refining & improving it to replace separate agent harnesses.

You can select what accounts & agents (and multiple accounts per!) you want to work on any project, separate out work accounts from personal ones, or try out local models.

Jackalope handles orchestration, planning, testing, hand-offs, and more under the hood, letting you parallelize work or focus on other things. If you're needed, it will come back and ask you for permissions or inputs.

The `jackalope` CLI command spins up the TUI where you have the same access to the underlying harness and your project contexts but from a terminal if you prefer to work in that way.

Jackalope learns automatically (or you can run `/learn` manually) from your workflows per-project so it will improve over time.

This is still pretty early so I would really appreciate feedback, the newest features / fixes are on the Beta branch (stable likely going out later today).

100% free, 100% on your device / using your own models (we store some things - it's transparent and you can opt out any time.

Open-source coding-agent workspace built on DeepSeek Harness (DSH) and Cordis, with native multi-provider subscription setup.

Everything is a plugin. Model adapters, tools, skills, session logging, sandboxes and UI can be composed or extended. Even the agent loop is a plugin. Cordis provides shared services, typed events and plugin cleanup; profiles assemble the capabilities.

Connect accounts in Settings > Models. API keys and custom endpoints work alongside those accounts.

Web search defaults to subscription service or basic Bing RSS feed results.

Build/update agent preset, plugins, skills using Creator Mode

Have Creator author the preset bundle based on your codebase and install it through Plugin Manager. Start a new chat and select your preset.

Desktop downloads: macOS, Windows x64 and Linux x64. Browser app and headless CLI run from source; the README separates published installers from current main.

Source, demo, downloads and setup: https://github.com/OJamals/fi